Fix DB schema version #374
Merged
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
To avoid pending migrations that cannot be run. The version was incorrectly de-incremented in a previous merge.
|
thanks for spotting! |
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.
I wanted to take a sneak peak at your work here @MartinHinz (which looks great, by the way!) and came across an issue with the database migrations. It looks like the schema version was incorrectly de-incremented in this merge, which meant Rails wanted to run the migrations to create the 'dendros' and 'chronologies' tables even though they already exist in the schema. Re-incrementing the schema version fixes this and allows the database to be cleanly regenerated.