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
While working on a new migration, it is annoying to have to drop and reapply a migration.
Proposed Solution: Consider migrations with WIP in their name, they will be applied, but they won't be recorded to the migrations table. This allows a single command ley up to reapply WIP migrations.
The text was updated successfully, but these errors were encountered:
Hmm, what would ley up do in the case of eg. CREATE TABLE? There would be a table already created and running this migration again would fail. If you mean that it would also run the down() function, that seems a bit unusual / unexpected.
Maybe it would be easier to create your own script in package.json which would run ley down && ley up?
While working on a new migration, it is annoying to have to drop and reapply a migration.
Proposed Solution: Consider migrations with
WIP
in their name, they will be applied, but they won't be recorded to the migrations table. This allows a single commandley up
to reapply WIP migrations.The text was updated successfully, but these errors were encountered: