-
-
Notifications
You must be signed in to change notification settings - Fork 360
Issues: db-migrate/node-db-migrate
New issue
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
error when initialization of migration failes before any action.
bug
#689
opened Apr 22, 2020 by
wzrdtales
No order is guaranteed if migrations have the same date
bug
feature
good first issue
help wanted
#646
opened Aug 28, 2019 by
abolognino
1 of 3 tasks
Properly use DATABASE_URL as per documentation
bug
#584
opened Sep 26, 2018 by
bill-kitsune
Loading…
Programmable API createDatabase arguments are overridden
bug
needs confirmation
#578
opened Jul 24, 2018 by
tjokimie
1 of 3 tasks
db-migrate fails to show version if database.json missing
bug
good first issue
help wanted
Nice to have
#568
opened May 8, 2018 by
vladimirtiukhtin
1 task
setting DATABASE_URL doesn't ignore defaultEnv from .db-migraterc
bug
#564
opened Apr 25, 2018 by
gudatcomputers
1 of 3 tasks
wrong formatted db-migrate db command should error out
bug
#556
opened Mar 21, 2018 by
aaronjameslang
1 of 3 tasks
sync operation with scope will fail with 'cannot find module' when migrate down
bug
needs confirmation
#471
opened Mar 30, 2017 by
jshencode
getInstance with only string not working
bug
Refactoring
#469
opened Mar 28, 2017 by
BorntraegerMarc
schema config parameter has no effect with pg driver (postgres)
bug
#459
opened Jan 23, 2017 by
stefaneg
When you trigger migration up or down programmatically, you cannot specify migration table in options
bug
#455
opened Jan 12, 2017 by
ghost
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.