#18748: Remove dupe-avoidance logic from the ORM
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Ready for
Severity: Normal | checkin
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
I did some digging, and the dupe avoidance seems to be about cases where
there are multiple paths from model A to model B, but through different
columns. Something like this:
{{{
class B:
pass
class A:
b1 = models.ForeignKey(B)
b2 = models.ForeignKey(B)
}}}
However, this case is already handled in join() by having the column in
the join identifier. That is, we will no accidentally reuse join through
b1 for b2.
To me it seems there is no need for dupe avoidance any more.
--
Ticket URL: <https://code.djangoproject.com/ticket/18748#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
