#17025: sql/where.py WhereNode refactoring
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.3
Component: Database layer | Resolution:
(models, ORM) | Triage Stage:
Severity: Normal | Unreviewed
Keywords: orm cleanup | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by Suor):
* cc: suor.web@… (added)
Comment:
Cleaning up sql.Query and its parts and optimizing SQL generation is a
kind of crusade, I feel, django needs.
Still your patch seems too hairy, perhaps the only way to make it clean is
even more radical approach of thorough refactoring both sql.Query and sql
compiler.
Also, when I profiled sql compilation I found that .get_columns() call is
way too slow, I didn't find any good solution at a time, but you seem to
be pretty familiar with orm internals. Maybe it will help.
--
Ticket URL: <https://code.djangoproject.com/ticket/17025#comment:2>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
