-
-
Notifications
You must be signed in to change notification settings - Fork 51
Issues: db-migrate/pg
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
"The driver you are using does not support the new state management."
#61
opened Dec 29, 2020 by
domarp-j
Feature Request - env. variable for setting migrations table schema DATABASE_SCHEMA
#57
opened Nov 24, 2020 by
alesmenzel
Grab an advisory lock for migration as per Heroku recommendations
#23
opened Sep 20, 2017 by
brabster
changeColumn doesn't take into account many column spec options
#18
opened May 5, 2017 by
justinnguyen
Datetime should be mapped to timesamp "with time zone" instead of "without time zone"
#12
opened Oct 13, 2016 by
fleebzz
Migration in a Postgresql database does not migrate in the specific schema.
question
#11
opened Oct 4, 2016 by
jun1111
Drop Db doesn't (can't) work if connected to the db you want to drop
bug
feature
#3
opened Jan 4, 2016 by
vertiman
createTable errors out when you specify length and autoincrement in postgres
bug
#1
opened Nov 7, 2015 by
wzrdtales
ProTip!
Add no:assignee to see everything that’s not assigned.