#26347: Saving ManyToMany field under race condition causes data loss
-------------------------------------+-------------------------------------
Reporter: hchargois | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: mysql transaction | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Could you check if you can reproduce with Django 1.9? It might be resolved
by the [https://docs.djangoproject.com/en/stable/releases/1.9/#related-
set-direct-assignment related set direct assignment] change.
If it's fixed in 1.9, I'm not sure if there's much value in patching
Django 1.8 as I assume this isn't a new issue and I'm not sure if it'd be
feasible to fix it without an invasive patch.
--
Ticket URL: <https://code.djangoproject.com/ticket/26347#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/067.f5e1436312335688cf8e2e00c2aaeece%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
