#16759: Expensive sql.Query cloning
-------------------------------------+-------------------------------------
Reporter: Suor | Owner: Suor
Type: Bug | Status: new
Component: Database layer | Version: 1.3
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Ready for
Keywords: orm performance | checkin
cloning | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
Constraint has .relabel_aliases, and thus is not immutable. It could of
course be made immutable by extensive changes to the code (relabel only at
as_sql time), but I don't think that is what is wanted in this ticket.
It would be good if somebody with real queryset cloning performance
problems could try the alternate patch. I have a feeling it could be
surprisingly big win in some cases.
--
Ticket URL: <https://code.djangoproject.com/ticket/16759#comment:10>
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 this group at
http://groups.google.com/group/django-updates?hl=en.
