I'd use git bisect to find the commit where the behavior changed in Django. That will likely yield some insight.
https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#bisecting-a-regression On Friday, March 9, 2018 at 5:39:43 PM UTC-5, Michael Soderstrom wrote: > > In a 1.11 branch I had a complex raw sql snippet added to a query set via > annotate. > > When I updated Django to 2.0, the query set behavior changed to include > the raw sql in the GROUP BY which destroyed the performance. > > The same behavior occurred using annotate and extra. > > I was able to hack around it by overwriting the get_group_by_cols on my > RawSQL instance to return an empty list, but that seems wrong. > > Is the new behavior a bug or a feature and is there a less hacky way of > handling this? > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/16fc7b70-ba9f-4761-b73c-7499a9b7a373%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
