#19726: Ordering on booleans works different with SQLite and Postgres
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
You're not missing anything bcail.
From the oldest versions of PostgreSQL (9.0.21 released in 2015), SQLite
(3.9.0 released in 2015), and MySQL (5.6.25 released in 2015) I could get
to run none of them exhibit the behaviour reported here.
All of them ordered false values before true ones so I believe this issue
might have been invalid all that time.
Thanks for surfacing bcail.
--
Ticket URL: <https://code.djangoproject.com/ticket/19726#comment:8>
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/01070183b0507a44-013ae839-99f6-4214-85fb-c4ed93b1c391-000000%40eu-central-1.amazonses.com.
