chore: Add info on known limitations wrt nested transactions #69
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
|
Published beta package version: |
Signed-off-by: Lucian Buzzo <[email protected]>
LucianBuzzo
force-pushed
the
lucianbuzzo/nest-transactions-limitation
branch
from
5a01259
to
616f508
Compare
|
SonarCloud Quality Gate failed.
|
SarjuHansaliya
approved these changes
Oct 11, 2023
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.
Yates uses a transaction to apply the RLS policies to each query. This means that if you are using transactions in your application, rollbacks will not work as expected. This is because Prisma has poor support for nested transactions and will
COMMITthe inner transaction even if the outer transaction is rolled back.If you need this functionality and you are using Yates, you can return
nullfrom thegetContext()setup method to bypass the internal transaction, and therefore the RLS policies for the current request. see thenested-transactions.spec.tstest case for an example of how to do this.