#23572: Exception on Custom Lookups when right value is None.
-------------------------------------+-------------------------------------
Reporter: maherma-adg | Owner:
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 nielsvanoch):
* owner: nielsvanoch =>
* status: assigned => new
Comment:
I had a look at this, but couldn't find a good place/pattern to put it in.
The problem is that the behavior of the two lookups that currently act
different (exact and iexact) is tricky to implement, because you need to
have already constructed your Lookup object, but then replace it by a
different one. If anyone has a good idea about a structure to solve this,
I'd be happy to take another crack (although realistically, that person
could probably also complete the patch easily).
--
Ticket URL: <https://code.djangoproject.com/ticket/23572#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/069.d180a15847d1ed981a85fb966b9b4e7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
