#22291: transactions.atomic (with savepoints) doesn't work correctly with
deadlocks
in mysql
-------------------------------------+-------------------------------------
Reporter: err | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.6
(models, ORM) | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by err):
* status: closed => new
* resolution: needsinfo =>
Comment:
>> I assume Django raises an exception when trying to rollback to the
savepoint that no longer exists
the problem is that Django is trying to rollback to the savepoint. this is
incorrect in mysql
--
Ticket URL: <https://code.djangoproject.com/ticket/22291#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/061.202287c05c6bb8e5fde4a48840950575%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
