#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:"58723722e90a1b34dc1c7ea020c8065755f9c927" 5872372]:
{{{
#!CommitTicketReference repository=""
revision="58723722e90a1b34dc1c7ea020c8065755f9c927"
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.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26162#comment:6>
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.dc010ccad12fa9109af4534c181ff95c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
