#19259: Annotations generating inefficient SQL on PostgreSQL
-------------------------------------+-------------------------------------
Reporter: hcarvalhoalves | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.4
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 0
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
I think the GROUP BY clause could be constructed using the select and
related_select_cols' field information. If a select column's field is
available, then include the field only if field.primary_key is True. If
the field isn't available, include it always in the GROUP BY.
For the version dependency there are other example of disabling/enabling
functionality based on version, at least regex searches on Oracle are
such. In any case, a separate backend for this is a no-go.
--
Ticket URL: <https://code.djangoproject.com/ticket/19259#comment:15>
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.
For more options, visit https://groups.google.com/groups/opt_out.
