#36407: Query compiler optimizes CASE..WHEN into a programming error on
Postgres 16
-------------------------------------+-------------------------------------
Reporter: deceze | Owner: ontowhee
Type: Bug | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
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 Simon Charette):
> Interestingly, Oracle does not sort as expected when casting.
This is because the order is ambiguous, ordering by a constant is the same
as not ordering by anything which means the database is allowed to return
results in whatever orders it wants.
This is not an issue with Oracle but with the test itself. It should order
by `pk` as well to make sure it matches the expected sequence.
--
Ticket URL: <https://code.djangoproject.com/ticket/36407#comment:5>
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 visit
https://groups.google.com/d/msgid/django-updates/01070196f9f0957d-97f1b0d3-52fe-4962-9971-ac65501507a9-000000%40eu-central-1.amazonses.com.
