#24767: Add GREATEST and LEAST Query Expressions
-------------------------------------+-------------------------------------
Reporter: Ian-Foote | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jarshwah):
The postgres behaviour is the more useful IMO but it's also the odd one
out. But that's why I suggested wrapping everything in a coalesce while
providing opt outs.
I don't think we'd be able to emulate other backend behaviour with
postgres anyway without quite complex case expressions.
So as far as I'm concerned, if you can provide an expression that works
for postgres and emulates postgres on other backends (with an opt out),
it'd be accepted into core. Happy to help if needed.
--
Ticket URL: <https://code.djangoproject.com/ticket/24767#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.fcc36cbe07a29764ef4480b72193eda0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
