Use semver directory to carry the schema version #930
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.
Hi,
This PR is an attempt to use semver directory to represent the schema version. The current version scheme is not intuitive and requires additional efforts to keep track of the database version with the application version.
This PR moves the version component from the file name to its containing directory. The name of directory conforms to the semver standard. Currently, this feature is available to the
file
source.In addition, there are two extra fields added to the
schema_migrations
table so that we can track when is the schema change applied last time as well as the change identifier w/ semver version number embedded.Please consider merge this PR or feel free to get back to me for further improvement.
Thanks for your attention!