Improved migrations version handling #29
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I always use timestamp migrations to ensure ordering.
Where does it say to use 001 and such? I definitely would not recommend that and it is wrong if I put that somewhere. |
|
Ah, thanks. Sorry about that! I created a new issue to update those docs. #30 Closing this out as we really should recommend timestamps. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the example in the migrations doc (using 001) as the prefix for my migration, and because I didn't read the disclaimer about the version numbers below 😁 , I've had problems with migrations ordering and once solved I found that padding versions with zeroes makes pending migrations method to fail and tries to rerun the migration. Fixed all of these relying on the version nummeric value rather than alphanummeric one.