Replies: 2 comments 1 reply
-
@mmkal can I get an answer? These errors do not allow me to use umzug |
Beta Was this translation helpful? Give feedback.
-
Comenting here from the sequelize perspective and not umzug specifically. The DeprecationWarnings that you are getting are from sequelize v7 alphas, and umzug officially does not support that yet. That's why you see those. But they're only warnings and not the casue of any issues. For the Sequelize constructor in the newest alpha, check out this documentation; https://sequelize.org/docs/v7/databases/postgres/ |
Beta Was this translation helpful? Give feedback.
-
Example.
When executing
ts-node migrate --help
errors:But the documentation says that it is necessary to use
context: _sequelize.gt queryinterface()
. Why is it suggested to usesequelize.queryInterface
?How should I use
sequelize.models.hasByName
? I didn't find anything in the documentation.ts-node migrate create --name tableA.ts
errors:Why is the configuration ignored in this case?
migrations: {glob: ['migrations/*.{ts,sql}', {cwd: __dirname}]}
When running
ts-node migrate create --name tableA.ts --folder migrations
an error occurs, the migration file is created, but the command does not end. Can you tell me what this error means?I did not find any information in the documentation to specify the user or database password for performing migrations. Tell me, it needs to be transferred to
const _sequelize = new Sequelize({ dialect: 'postgres', logging: console.log });
?Beta Was this translation helpful? Give feedback.
All reactions