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
a difference between your driver and others is that no callback is ever caller after all migrations is applied:
DBMigrate.getInstance(true,{}) .sync() .then(() =>console.log('migration done')) .catch((err) => console.log('migration failed', err))
will never have his then or catch called
I found that the source of this problem is that you never call the provided callback during driver.close(cb);
this callback is responsible for terminating the promise of all operations. (see db-migrate/lib/commands/on-complete.js:11)
do you still maintains this repository, and if so, would you merge a PR that fix this bug if I fill one ?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
a difference between your driver and others is that no callback is ever caller after all migrations is applied:
will never have his then or catch called
I found that the source of this problem is that you never call the provided callback during driver.close(cb);
this callback is responsible for terminating the promise of all operations. (see db-migrate/lib/commands/on-complete.js:11)
do you still maintains this repository, and if so, would you merge a PR that fix this bug if I fill one ?
The text was updated successfully, but these errors were encountered: