#28553: Querysets: annotate() columns are forced into a certain position which
may
disrupt union()
-------------------------------------+-------------------------------------
Reporter: David Sanders | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Kal Sze):
Actually there could be a different problem as well. We were lucky in that
the ORM generated SQL where the column types do not match. But what
happens when the column types match? I'm afraid you would get a query that
doesn't throw an exception but is in fact subtly broken, especially if the
values of the differnet columns happen to be similar, in which case it
might take a long time for app developers to realize that the query is
broken.
--
Ticket URL: <https://code.djangoproject.com/ticket/28553#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.0210d2d5e226fab653d31c0ceebd6c15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
