#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 anonymous):
Could be a right approach but for slightly different problem. We are
trying to fix bug here, you are making cleanup. Though your cleanup fixes
a problem too.
Regarding patch, as I understand django backward compatibility policy,
internal things like sql.Query or tree.Node are not guaranteed to be
backward compatible, so you should not complicate your code with catching
AttributeErrors and fallbacking to deepcopy. Just take your idea of
replacing deepcopy with .clone() to its logical end.
--
Ticket URL: <https://code.djangoproject.com/ticket/16759#comment:8>
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.
