#34798: Using Django 4.2 with MSSQL 2019 Aggregation Containing Subquery Fails
-------------------------------------+-------------------------------------
Reporter: Haldun Komsuoglu | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: MSSQL, Aggregation, | Triage Stage:
Subquery | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
This seems to be related to #34551 somehow. The `refs_subquery` check
added in e5c844d6f2a4ac6ae674d741b5f1fa2a688cedf4 is not transitive in the
sense that it would work in cases where `exchange` is referenced directly
but not when not through combined expression. I'm surprised that the test
added there doesn't fail if the aggregation is made through another `F`
annotation referring the subquery annotation.
--
Ticket URL: <https://code.djangoproject.com/ticket/34798#comment:3>
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/0107018a2ce3f46d-b1b27115-7c86-4812-8c3f-8fb752e51635-000000%40eu-central-1.amazonses.com.
