#20571: Using savepoints within transaction.atomic() can result in the entire
transaction being incorrectly and silently rolled back
-------------------------------------+-------------------------------------
Reporter: lamby | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version:
(models, ORM) | 1.6-alpha-1
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* severity: Normal => Release blocker
* needs_better_patch: => 0
* needs_tests: => 0
* version: 1.5 => 1.6-alpha-1
* needs_docs: => 0
* type: Uncategorized => Bug
* stage: Unreviewed => Accepted
Comment:
Ill mark this as release blocker, seems like some solution is going to be
needed... I haven't tested anything, but I feel confident enough in the
report to just mark this accepted, too.
I wonder if savepoint_commit() and savepoint_rollback() could just mark
the transaction block as "correct" again. Wouldn't this solve the problem?
--
Ticket URL: <https://code.djangoproject.com/ticket/20571#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.12158cf919b9e2b781cd2a6106db02d6%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
