We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From TG
@Kouprin
I'm trying to start https://github.com/near/near-contract-helper
I've created accounts_development database as required and yarn migrate execution is failed. What is missing?
@mattlockyer
Not sure if this helps but we updated sequelize-cli (the only issue I can think of related to migrations)
Try downgrading temporarily to run the migrations for setup and then you can bump back up.
Or I would google this particular issue with sequelize migrations (likely an issue from 5 - 6 they changed the format for specifying the constraints)
For versions of sequelize we used before see this: 3bf7986
you are perfectly right, downgrading has helped thank you!
The text was updated successfully, but these errors were encountered:
@vgrichina should we update migration files or downgrade sequelize?
Not sure how you feel re: trade-offs?
Sorry, something went wrong.
@mattlockyer upgrade migration files. Change is trivial and we don't want to be stuck on old unsupported versions because of this.
No branches or pull requests
From TG
@Kouprin
I'm trying to start https://github.com/near/near-contract-helper
I've created accounts_development database as required and yarn migrate execution is failed. What is missing?
@mattlockyer
Not sure if this helps but we updated sequelize-cli (the only issue I can think of related to migrations)
Try downgrading temporarily to run the migrations for setup and then you can bump back up.
Or I would google this particular issue with sequelize migrations (likely an issue from 5 - 6 they changed the format for specifying the constraints)
For versions of sequelize we used before see this:
3bf7986
@Kouprin
you are perfectly right, downgrading has helped
thank you!
The text was updated successfully, but these errors were encountered: