Introduce a new rule to lint nested transactions #303
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
Since PostgreSQL doesn't support true nested transactions, this rule looks for transaction managements statements that might cause problems when running migrations, like BEGIN or COMMIT being issued multiple times. It also enforces strictness around assume-in-transaction: the migration tool is in charge of the transaction and explicit BEGIN/COMMIT statements may cause problems.
👷 Deploy request for squawkhq pending review.Visit the deploys page to approve it
|
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.
Since PostgreSQL doesn't support true nested transactions, this rule looks for transaction managements statements that might cause problems when running migrations, like BEGIN or COMMIT being issued multiple times. It also enforces strictness around assume-in-transaction: the migration tool is in charge of the transaction and explicit BEGIN/COMMIT statements may cause problems.