#19726: Ordering on booleans works different with SQLite and Postgres
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.4
(models, ORM) | Resolution: wontfix
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
This is one of those situations where the bug report is 100% correct, but
we mark the bug wontfix anyway.
Although Django's ORM is an abstraction over the database providing some
measure of database independence, it doesn't mean you can completely stop
caring about the underlying data store. There are many subtle differences
between backends, ranging from handling of different datatypes, ordering,
all the way to performance considerations.
"Fixing" this sort of problem would require a lot of code, would probably
make the SQLite backend more fragile (since it would be more complex), and
would ultimately only help one specific type of use case -- the developer
who switches databases between development and production. I'm not
convinced this is a cost worth assuming, so I'm marking this wontfix.
--
Ticket URL: <https://code.djangoproject.com/ticket/19726#comment:2>
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.
For more options, visit https://groups.google.com/groups/opt_out.
