#21524: Annotation and .extra with group function breaks at database level
-------------------------------------+-------------------------------------
     Reporter:  eu@…                 |                    Owner:  nobody
         Type:  Uncategorized        |                   Status:  new
    Component:  Database layer       |                  Version:  1.4
  (models, ORM)                      |               Resolution:
     Severity:  Normal               |             Triage Stage:
     Keywords:  oracle               |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by aaugustin):

 You're clearly pushing the boundaries of what the ORM can do... Writing
 the query in plain SQL (look for raw SQL in the documentation) could be
 easier at this point — and a short term solution.

 I'll let someone who knows the aggregation code better than me make a
 decision on this ticket.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/21524#comment:2>
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/074.9c611072be9274404f1f6b5aece3fd06%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to