You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per the discussion in #91, currently, there is no mechanism to update shorthands in tandem with migrations, in the case where a field that uses a shorthand ever needs to change in the future. I propose that we allow the ability to define shorthands within migration files, so that they can be updated.
Since changing a shorthand doesn't actually change anything unless a migration is run that uses it, an explicit call to pgm.alterColumn will be required.
As per the discussion in #91, currently, there is no mechanism to update shorthands in tandem with migrations, in the case where a field that uses a shorthand ever needs to change in the future. I propose that we allow the ability to define shorthands within migration files, so that they can be updated.
Since changing a shorthand doesn't actually change anything unless a migration is run that uses it, an explicit call to
pgm.alterColumn
will be required.1234567890-create-user-table.js:
1234567891-update-user-table.js:
This also keeps all information relevant to migrations within the migration files. Discussion and/or improvements welcome.
The text was updated successfully, but these errors were encountered: