#22291: transactions.atomic (with savepoints) doesn't work correctly with
deadlocks
in mysql
-------------------------------------+-------------------------------------
Reporter: err | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.6
(models, ORM) | Resolution: needsinfo
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
-------------------------------------+-------------------------------------
Comment (by err):
I thing Django should rollback whole transaction and raise normal error
django.db.utils.OperationalError: (1213, 'Deadlock found when trying to
get lock; try restarting transaction') not
django.db.utils.OperationalError: (1305, 'SAVEPOINT s139640098436864_x1
does not exist')
--
Ticket URL: <https://code.djangoproject.com/ticket/22291#comment:2>
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.86010ff290de19414a9240c31916d22e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
