Dumps the schema or structure of a database when calling db:migrate:name #38586
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
|
Force pushed to trigger a build. Buildkite didn't seem to pick up the initial commit. |
|
Can you rebase this? I think your last PR conflicts with this one. |
|
Yep, will do 👍 |
Rebased and the build is green ✨ |
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.
Summary
In previous versions of Rails,
rails db:migratewould dump the schema of the database. In Rails 6, that holds true (rails db:migratedumps all databases' schemas), butrails db:migrate:namedoes not share that behavior.Going forward, this change would have calls to
rails db:migrate:namedump the schema (or structure) of the database being migrated (builds on the work in #38449)