#33282: django.db.utils.ProgrammingError: more than one row returned by a
subquery
used as an expression
-------------------------------------+-------------------------------------
Reporter: Antonio Terceiro | Owner: Simon
| Charette
Type: Bug | Status: closed
Component: Database layer | Version: 3.2
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"e5a92d400acb4ca6a8e1375d1ab8121f2c7220be" e5a92d4]:
{{{
#!CommitTicketReference repository=""
revision="e5a92d400acb4ca6a8e1375d1ab8121f2c7220be"
Fixed #33282 -- Fixed a crash when OR'ing subquery and aggregation
lookups.
As a QuerySet resolves to Query the outer column references grouping logic
should be defined on the latter and proxied from Subquery for the cases
where
get_group_by_cols is called on unresolved expressions.
Thanks Antonio Terceiro for the report and initial patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/33282#comment:14>
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/066.dabb4debc478b811f442019732a43925%40djangoproject.com.
