#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 mtredinnick):
Alex pinged me to take a look at this. I am *very* suspicious of removing
exclusions from the "def join(...)" part. I have a memory it was important
at the time. The reason for this being there may have vanished in the
interim (it was 5 years ago and prior to the SQL-compiler changes), but
I'll try to puzzle it out this weekend.
The reason for it would have been to avoid inadvertent merging of table
joins when we need to force joining separate copies of the same table. On
the other hand it's been around much longer than the real monster join
bugs prior to 1.0, so the effect may be duplicated in other code, removing
the need for this,
--
Ticket URL: <https://code.djangoproject.com/ticket/18748#comment:5>
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.
