Add file name also on schema_migrations #484
ap-in-git
started this conversation in
Feature Ideas
Replies: 2 comments 1 reply
-
I think that's ok, as long as we still only compare the version number (i.e. if you rename a file, but keep the same version number, it still counts as applied). I would probably use the migration name rather than the full file name. Also, there will need to be smooth and backwards-compatible upgrade path. |
Beta Was this translation helpful? Give feedback.
0 replies
-
What's the status of this? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I think it would be better if we can add a file name also on schema_migrations other than versions. It makes things things easier to understand when you see schema_migrations to know what migrations has been applied.
For e.g. Laravel migrations schema keeps the file name also on migrations table.
If this features sounds okay. Maybe I can start working on PR for the pull request?
Beta Was this translation helpful? Give feedback.
All reactions