#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 -------------------------------------+------------------------------------- Changes (by aaugustin):
* status: new => closed * needs_docs: => 0 * resolution: => needsinfo * needs_tests: => 0 * needs_better_patch: => 0 Comment: I assume Django raises an exception when trying to rollback to the savepoint that no longer exists, which eventually leads to the entire transaction being rolled back. This appears to be the correct behavior. What do you suggest Django should do instead? -- Ticket URL: <https://code.djangoproject.com/ticket/22291#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 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.7f1a5e475703a781c3814cfb70cb0d3c%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.