Simplify DatabaseMigrator API #709
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
This method is now equivalent to registerMigration, starting SQLite 3.7.16
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.
All GRDB migrations now run with deferred foreign key checks, removing the need for two distinct methods
DatabaseMigrator.registerMigration()andDatabaseMigrator.registerMigrationWithDeferredForeignKeyCheck(). The latter is deprecated in favor of the other.In previous GRDB versions, foreign key violations executed by a migration would immediately throw an error. Now those violations still throw an error, but at the end of the migration.