Add run_through_version method for versioned migrations#3878
Open
breuhan wants to merge 1 commit into
Open
Conversation
Collaborator
|
I already have a similar change in https://github.com/launchbadge/sqlx/pull/3383/files#diff-93b9b9f2d9c2f7fe607f3fca79da6def6664450fe4105f0f3d1c3478fd5d2a32R160 |
Author
|
Yes it is a similar change, but on a deeper level. What is missing from that PR is the query for the latest applied migration and the query for the latest_version() from the Migration source. I'm also happy if that could be integrated. |
This file contains hidden or 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.
Description:
The sqlx library already has a feature in sqlx-cli https://github.com/launchbadge/sqlx/blob/main/sqlx-cli/src/migrate.rs
To run migration till a specific version. Unfortunately this functionality isn't yet exposed to the library.
Therefore, this PR introduces three new public functions to the
Migratorstruct:latest_version(): Returns the highest version number among all migrations defined in theMigrator's source.latest_applied_version(): Retrieves the highest version number of migrations that have already been successfully applied to the database.run_through_version(target: i64): Allows running "up" migrations against the database specifically up to atargetversion. This is enabling users to apply only a subset of pending migrations.I also added tests to run the new functionality against different database backends.
Is this a breaking change?
no, everything is backwards and forwards compatible. Only added function