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

Not loading filesystem migrations when migrating down to a different app. #2

Open
seanharrison opened this issue Sep 23, 2024 · 0 comments

Comments

@seanharrison
Copy link
Collaborator

  • When a "dn" migration in your app's filesystem migrations differs from the ones applied in the database,
  • and the specified target "to" migration is in a different app (such as migrating down to the sqly init migration),
  • then the app's filesystem migrations are not loaded,
  • so the db-loaded migration is used.
  • This can be vexing when bugfixing a dn migration, because the filesystem (corrected) migration is not loaded.

Workaround for now is not the migrate to a different app when bugfixing.

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

1 participant