Opened 15 years ago
Closed 14 years ago
#11576 closed (duplicate)
FilterSpec and Null values
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | contrib.admin | Version: | 1.0 |
Severity: | Keywords: | FilterSpec | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
FilterSpec don't do much at the moment concerning fields that accept Null values.
I patched DateFieldFilterSpec to fix this issue.
I believe the same can be done for the rest of the FilterSpec.
For the BooleanFieldFilterSpec, I wonder why not checking self.field.null instead of requiring the developers to define a NullBooleanField in their model.
Attachments (2)
Change History (4)
by , 15 years ago
Attachment: | filterspecs.py.patch added |
---|
by , 15 years ago
Attachment: | filterspecs.py.2.patch added |
---|
comment:1 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|
Note:
See TracTickets
for help on using tickets.
Proper SVN patch