#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: assigned
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Raphael Michel):
* owner: nobody => Raphael Michel
* status: new => assigned
* has_patch: 0 => 1
Comment:
It is possible to solve the problem with an one-line patch. I created a
pull request for it: https://github.com/django/django/pull/9388/files
There might be more elegant solutions or solutions that solve the problem
more deeply because it might exist in other places as well, but I did not
come up with one in the available time.
It would be great to see this get into 2.0 or even a 1.11.8 if there will
be one!
--
Ticket URL: <https://code.djangoproject.com/ticket/28848#comment:1>
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.eae6856a7d951ccf758d4da6b8c812e5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
