Skip to content
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

Allow WIP migrations. #40

Open
eduardvercaemer opened this issue Mar 31, 2024 · 1 comment
Open

Allow WIP migrations. #40

eduardvercaemer opened this issue Mar 31, 2024 · 1 comment

Comments

@eduardvercaemer
Copy link

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.

@karlhorky
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants