Fix column order in schema file #3533
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
|
Travis build failed because of issue #3035, not related to this pull request. |
microweb10
approved these changes
May 24, 2019
When introducing Rails 5 and the dashboard, we generated the schema file without dropping the database first. When doing so locally, migrations aren't always executed in order, changing the order of the columns.
javierm
force-pushed
the
regenerate_schema
branch
from
10ea419
to
24236e6
Compare
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.
Objectives
Use a
schema.rbfile consistent with the one generated during a fresh installation.Notes
When introducing Rails 5 and the dashboard, we generated the schema file without dropping the database first. When doing so locally, migrations aren't always executed in order, changing the order of the columns.