-
Notifications
You must be signed in to change notification settings - Fork 0
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
Database transactions should be explicitly handled by the runner #37
Comments
swrichards
added a commit
that referenced
this issue
Dec 18, 2024
swrichards
added a commit
that referenced
this issue
Dec 18, 2024
swrichards
added a commit
that referenced
this issue
Dec 18, 2024
swrichards
added a commit
that referenced
this issue
Dec 18, 2024
swrichards
added a commit
that referenced
this issue
Dec 19, 2024
swrichards
added a commit
that referenced
this issue
Jan 20, 2025
swrichards
added a commit
that referenced
this issue
Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, only the management command is wrapped in a transaction block, which works fine for the common usage pattern, but does not transfer to e.g. testing contexts and generally leaves a bit of ambiguity around transactions. This should be explicitly handled in the runner.
The text was updated successfully, but these errors were encountered: