#24431: Combining extra(), annotate() or distinct() and count() can generate
invalid SQL
-------------------------------------+-------------------------------------
     Reporter:  briankrznarich       |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  Database layer       |                  Version:  1.8beta1
  (models, ORM)                      |
     Severity:  Release blocker      |               Resolution:
     Keywords:  extra distinct       |             Triage Stage:  Accepted
  aggregate count annotate           |
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  1                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by akaariai):

 Not having the required aliases for extra select clauses is exactly the
 reason why extra needs to be replaced. We aren't going to (and can't) fix
 all the issues related to extra usage.

 I think we can close this one. If we get more reports for the regression
 part of the bug report, and if that one is easy to fix, then lets
 reconsider fixing that part.

--
Ticket URL: <https://code.djangoproject.com/ticket/24431#comment:9>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.c42d029c11114702ff3f4eefe783e6ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to