#28848: nulls_first on SQLite can not be used on the result of a filtered
subquery
-------------------------------------+-------------------------------------
Reporter: Raphael Michel | Owner: Raphael
| Michel
Type: Bug | Status: closed
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"75c1fd653858997449f7ac47a3f3379723bbfc73" 75c1fd6]:
{{{
#!CommitTicketReference repository=""
revision="75c1fd653858997449f7ac47a3f3379723bbfc73"
[2.0.x] Fixed #28848 -- Fixed SQLite/MySQL crash when ordering by a
filtered subquery that uses nulls_first/nulls_last.
Backport of 616f468760e4984915bb2ccca6b9eb3d80ddadb0 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28848#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 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.494665c07dc913d39a80e2bda92f66af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
