#33768: MySQL ordering of nulls last/first is broken in combination with UNION
-------------------------------------+-------------------------------------
Reporter: Florian Apolloner | Owner: Aniruddh
| Singh
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(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 Florian Apolloner):
Hi Simon, sorry I lost track of this one in my mails.
> From my understanding and testing engines locally it seems that all
engines allow to refer to the first query member of the union by column
aliases just like by index
Interesting, that would be great indeed. I think I might have had issues
with UNION at the time I implemented it but if aliases work around the
board, that would be preferably imo.
> we could entirely drop the specialized combinator logic that uses RawSQL
to order by column index?
Hopefully yes :)
--
Ticket URL: <https://code.djangoproject.com/ticket/33768#comment:7>
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/01070181b87a6402-64224914-5bc8-46eb-adb2-b71979d5df40-000000%40eu-central-1.amazonses.com.
