#23572: Exception on Custom Lookups when right value is None.
-------------------------------------+-------------------------------------
Reporter: maherma-adg | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: 1.7
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: custom lookup, db | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
Yes, it seems this check belongs to the Lookup (with a base implementation
that raises the ValueError).
BTW you are likely going to stumble upon some other limitations in the
current Lookup implementation. A `.exclude(duration__ne=None)` call might
not work as expected (that is, return complement of
`.filter(duration__ne=None)`).
--
Ticket URL: <https://code.djangoproject.com/ticket/23572#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/069.d10e8d5c25efcdafc2c04df7aa0a408a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
