#37140: Document how to handle NULL when using filter()/exclude() with __in
subqueries
-------------------------------------+-------------------------------------
Reporter: Sebastian Vera | Owner: (none)
Type: Bug | Status: new
Component: Documentation | Version: dev
Severity: Normal | Resolution:
Keywords: exclude in subquery | Triage Stage: Accepted
NULL NOT IN |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by SnippyCodes):
I'd like to take this over! I will update the __in field lookup
documentation to warn about the NULL subquery behavior for both filter()
and exclude(). Following Simon's advice, I will document
filter(inner_field__isnull=False) as the recommended workaround.
--
Ticket URL: <https://code.djangoproject.com/ticket/37140#comment:7>
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/0107019ed3f4ca15-6c011435-c8eb-42e6-9424-1067a4ebde06-000000%40eu-central-1.amazonses.com.
