-
-
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
When you trigger migration up or down programmatically, you cannot specify migration table in options
bug
#455
opened Jan 12, 2017 by
ghost
Allow to disable transactional migrations per migration
feature
#424
opened Oct 7, 2016 by
User4martin
EventEmitter memory leaks
good first issue
help wanted
Refactoring
#421
opened Oct 4, 2016 by
foysavas
Is there a way to hook into an "afterMigrate" event?
documentation
feature
good first issue
help wanted
#384
opened Jul 11, 2016 by
mpalmerlee
Add a docker configuration to ease testing
feature
good first issue
help wanted
#372
opened May 11, 2016 by
Maxwell2022
Option to reference migrations by SemVer version rather than date
feature
#354
opened Feb 19, 2016 by
gilly3
Support "databaseless" execution commands
feature
good first issue
help wanted
#338
opened Jan 17, 2016 by
wzrdtales
Create a toolset to check the current configuration for issues
feature
#312
opened Sep 21, 2015 by
wzrdtales
Read database passwords from my.cnf, .pgpass file or other stand
feature
#310
opened Sep 19, 2015 by
MattMorgis
Add ability to use IDENTITY instead of SERIAL on Redshift
feature
#291
opened Aug 12, 2015 by
wzrdtales
Need ability to add "ON UPDATE" and non-escaped values
feature
#172
opened Jun 17, 2014 by
ericnakagawa
ProTip!
Exclude everything labeled
bug
with -label:bug.