Opened 10 years ago

Closed 10 years ago

Last modified 9 years ago

#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: UI/UX:


The documentation for queryset field lookups in 1.0 ( 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).

Change History (3)

comment:1 Changed 10 years ago by James Bennett

Resolution: fixed
Status: newclosed

(In [9105]) Fixed #9255: Removed now-obsolete warning about the old semantics of exact=None vs. isnull=True

comment:2 Changed 10 years ago by James Bennett

(In [9106]) [1.0.X] Apply doc fix from [9105]; refs #9255.

comment:3 Changed 9 years ago by (none)

milestone: post-1.0

Milestone post-1.0 deleted

Note: See TracTickets for help on using tickets.
Back to Top