#28553: Querysets: annotate() columns are forced into a certain position which
may
disrupt union()
-------------------------------------+-------------------------------------
Reporter: David Sanders | Owner: David
| Wobrock
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(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
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
#28900 seems to be an even more complex case where none of the combined
queries use explicit `values` but the result of the query combination
does.
In the comment:3 example both queries use `values` but happen to mix field
references and annotations which is not covered by the test included in
d6b6e5d0fd4e6b6d0183b4cf6e4bd4f9afc7bf67.
I'm bringing this up because most if not all of the changes made to
`sql.Query` for change the type of `annotation_mask` are unnecessary to
solve #28553 entirely.
--
Ticket URL: <https://code.djangoproject.com/ticket/28553#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018715472445-066c51be-eed9-49e0-9eae-ec533d20233f-000000%40eu-central-1.amazonses.com.
