#12725: Combining Q objects with | is inefficient; lots of deep cloning
---------------------------------------------------+------------------------
Reporter: jbalogh | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2-alpha
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by Alex):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
ISTM if this optimization is really worth it (and I don't know what your
usecase is), it should be done in _combine at the base class level in
django.utils.tree. Specifically if the RHS has the same combinator type
as the operator being preformed than the new node can be created by just
doing a list addition on the lists of children.
--
Ticket URL: <http://code.djangoproject.com/ticket/12725#comment:1>
Django <http://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-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
