#23557: annotate gives different results on postgresql and mysql
-------------------------------------+-------------------------------------
Reporter: brian | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by shaib):
It should be noted that "full" group-by causes significant performance
degradations on mysql; this is related to #17144.
In other respects, @jarshwah's comments are mostly correct -- except for
one point, and that is that the SQL spec is retarded, and an ORM ''can''
know when it's safe to group by a subset of the retrieved fields (which
are unique for the group).
I suspect the only way to resolve this without breaking stuff is to close
this ticket as "wontfix".
--
Ticket URL: <https://code.djangoproject.com/ticket/23557#comment:4>
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/063.a1093d7bcbd646678ba0fe4e9893de18%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
