Remind about statement breakpoints when mentioning manual sqlite migrations #2871
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
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.
Inspired by #1968 (and my own experience, and the experience of my colleague @stephlow)
This PR updates an error message that happens for sqlite databases when you attempt to rename a column.
The message encourages you to write a manual migration, but this can prove tricky for sqlite users because you MUST remember to include statement breakpoints in your migration.
The error message now contains a link to the originating issue as well as a reminder to use statement breakpoints. May this help the future generations.
In short: This PR is for our children's children.