#31376: Avoid unnecessary null checks ordering when possible on database that
don't
support NULLS (FIRST|LAST).
-------------------------------------+-------------------------------------
Reporter: Simon Charette | Owner: Simon
Type: | Charette
Cleanup/optimization | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | 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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"9f07f27124540e27b4c3140235da375b974c4175" 9f07f271]:
{{{
#!CommitTicketReference repository=""
revision="9f07f27124540e27b4c3140235da375b974c4175"
Fixed #31376 -- Optimized nulls ordering when possible on SQLite and
MySQL.
Both backends order NULLs first on ascending ordering and last on
descending ordering which makes ORDER BY IS (NOT)? NULL wasteful when
asc(nulls_first) and desc(nulls_last) are used since it prevents indice
usage.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31376#comment:3>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.d7111cc695f71a7bb0a678bfb5dc8b73%40djangoproject.com.
