Ignore duplicate inferred migrations having the same timestamp #369
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
andrew-farries
changed the title
exekias
reviewed
Jul 9, 2024
exekias
approved these changes
Jul 9, 2024
We assume that if there are multiple inferred migrations with the same timestamp and the same `up` SQL that they are part of a multi-statement batch. In those cases we are only interested in the last migration in the batch.
andrew-farries
force-pushed
the
fix-duplicate-batched-migrations
branch
from
036a2e0
to
093f92e
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.
Remove all but the last inferred migration in a group of inferred migrations that occur at the same timestamp with the same migration SQL.
Such inferred migrations are typically part of a batched transaction for which we want to ignore all but the effect of the last statement in the batch.