#35369: MySQL .union().aggregate() raises Unknown Column
-------------------------------------+-------------------------------------
Reporter: DS/Charlie | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 5.0
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage:
union,aggregate,mysql | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* resolution: => duplicate
* status: new => closed
Comment:
Per
[https://docs.djangoproject.com/en/5.0/ref/models/querysets/#django.db.models.query.QuerySet.union
the documentation]
> In addition, only LIMIT, OFFSET, COUNT(*), ORDER BY, and specifying
columns (i.e. slicing, count(), exists(), order_by(), and
values()/values_list()) are allowed on the resulting QuerySet. Further,
databases place restrictions on what operations are allowed in the
combined queries.
Closing as duplicate of #28519.
--
Ticket URL: <https://code.djangoproject.com/ticket/35369#comment:4>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018ed359f109-7d11113b-9eeb-45db-adca-ad9e7c6f7a3b-000000%40eu-central-1.amazonses.com.
