#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 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* stage: Accepted => Ready for checkin
Comment:
I am not too afraid re the code changes, the bigger question is if there
is something the dedupe logic is doing and I just haven't spotted it. To
me it seems there isn't. The code creates same amount of joins and the
generated queries are correct, at least according to test suite.
Todays useless fact: There are 29176 instances of the word 'JOIN' in SQL
executed by the testing framework (both with and without patch).
Marking again RFC.
--
Ticket URL: <https://code.djangoproject.com/ticket/18748#comment:4>
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.
