-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transaction management #131
Comments
Error message should suggest reading the |
May be a check if validate is not running in an atomic context should be fine? |
WhyNotHugo
pushed a commit
that referenced
this issue
May 24, 2022
WhyNotHugo
pushed a commit
that referenced
this issue
May 24, 2022
WhyNotHugo
pushed a commit
that referenced
this issue
May 24, 2022
WhyNotHugo
pushed a commit
that referenced
this issue
May 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Validating recepts handles DB transactions by itself just fine.
Using this can be dangerous:
If there's a failure during this call, the can be irrecoverable data loss.
validate()
should internally check that no transaction is ongoing, andraise ProgramingError()
if it is being run inside a transaction.The text was updated successfully, but these errors were encountered: