#32995: Incorrect GROUP BY in ORM query with Function
-------------------------------------+-------------------------------------
Reporter: Joshua "jag" | Owner: nobody
Ginsberg |
Type: Bug | Status: new
Component: Database layer | Version: 3.1
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Joshua "jag" Ginsberg):
* status: closed => new
* resolution: needsinfo =>
Comment:
I think I found the issue/discrepancy between the model snippet and my
actual one: the default ordering for queries included `called_at` -- which
seems to have affected the GROUP BY, even though `called_at` wasn't in the
query and the resulting SQL didn't have an ORDER BY clause.
This feels like a bug, though not the one I originally believed. Thoughts?
--
Ticket URL: <https://code.djangoproject.com/ticket/32995#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.ed67f004ca5b028d03e56c8bedb74c6e%40djangoproject.com.
