#6707: ManyToManyField clears and recreates all data
-------------------------------------+-------------------------------------
Reporter: favo <favo@…> | Owner: loic
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Loic Bistuer <loic.bistuer@…>):
In [changeset:"20eb51ce0ddcb8d5fdc772fc2839fefef5b28c2a"]:
{{{
#!CommitTicketReference repository=""
revision="20eb51ce0ddcb8d5fdc772fc2839fefef5b28c2a"
Fix small regression caused by 71ada3a8e689a883b5ffdeb1744ea16f176ab730.
During direct assignment, evaluating the iterable before the transaction
is started avoids leaving the transaction dirty if an exception is raised.
This is slightly more wasteful but probably not enough to warrant a change
of behavior.
Thanks Anssi for the feedback. Refs #6707.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/6707#comment:41>
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/080.7e58ccfd498b98f670f714b214de525e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
