#9255 closed (fixed)
Documentation on queryset __exact=Null vs __isnull=True is contradictory.
Reported by: | Cliff Dyer | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.0 |
Severity: | Keywords: | queryset exact isnull | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
The documentation for queryset field lookups in 1.0 (http://docs.djangoproject.com/en/dev//ref/models/querysets/#id7) is self-contradictory. Under EXACT, it says that the semantics of idexact=Null has been changed in 1.0 to mimic the behavior of idisnull=True. Under ISNULL, it says that idexact=Null never returns anything (the old behavior).
Note:
See TracTickets
for help on using tickets.
(In [9105]) Fixed #9255: Removed now-obsolete warning about the old semantics of exact=None vs. isnull=True