#26162: Data loss when ManyToManyField refers to the wrong table
-------------------------------------+-------------------------------------
Reporter: Ian-Foote | Owner: charettes
Type: Bug | Status: closed
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette <charette.s@…>):
In [changeset:"edff550392d7fb23ad42119f31615bded571d6e0" edff550]:
{{{
#!CommitTicketReference repository=""
revision="edff550392d7fb23ad42119f31615bded571d6e0"
[1.8.x] Fixed #26162 -- Checked query name clashes of hidden
relationships.
Although reverse accessor clashes should be skipped query name can't be
hidden.
Thanks to Ian Foote and Tim Graham for the review.
Backport of a325fb1f9b14b46288d0e1342407be4a6db2bdb1 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26162#comment:7>
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/067.6835660e47a484e9762a3f49bb08538d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
