#25946: Negated clauses' "isnull" added term does not take field transforms into
account
-------------------------------------+-------------------------------------
Reporter: ris | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: transform negated | Triage Stage: Accepted
null |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by akaariai):
* needs_better_patch: => 0
* stage: Unreviewed => Accepted
* needs_tests: => 0
* needs_docs: => 0
Comment:
Yes, we need a fix here. At least we need to mark if
transforms/expressions are nullable, and then do the IS NOT NULL check
against the transformed value.
I don't think we can go for the coalesce solution, it is likely a lot
slower than using the current two-conditions-ANDed approach.
--
Ticket URL: <https://code.djangoproject.com/ticket/25946#comment:1>
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/061.89826154ea9d76a190bea57159162e7b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
