#24020: Use expressions in ORM internals -------------------------------------+------------------------------------- Reporter: akaariai | Owner: nobody Type: | Status: new Cleanup/optimization | Version: master Component: Database | Keywords: layer (models, ORM) | Has patch: 1 Severity: Normal | Needs tests: 0 Triage Stage: Accepted | Easy pickings: 0 Needs documentation: 0 | Patch needs improvement: 1 | UI/UX: 0 | -------------------------------------+------------------------------------- We should use expressions instead of tuples of form (alias, column, field) when calculating the select, order_by and group by clauses of the ORM. The WHERE clause already uses lookups, and joins were made to use Join classes. This would finalize usage of expression like objects throughout the query compiling process.
-- Ticket URL: <https://code.djangoproject.com/ticket/24020> 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 unsubscribe from this group and stop receiving emails from it, send an email to django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/051.85c48a05b696e43222c3bf35381531f7%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.