#13071 closed (fixed)
NullBooleanField save error in Admin?
| Reported by: | Ed Hagen | Owned by: | nobody | 
|---|---|---|---|
| Component: | Contrib apps | Version: | 1.2-beta | 
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no | 
| Needs tests: | no | Patch needs improvement: | no | 
| Easy pickings: | no | UI/UX: | no | 
Description
I have a model field defined thus: 
benefit = models.NullBooleanField()
In django 1.1 and 1.2 pre-alpha, nulls were displayed with a "?" icon 
in list view. In the Admin change form, a pop-up menu appeared with 3 
options (Unknown, Yes, No). Setting to "Unknown" and saving did not 
generate any errors. 
I then updated to django 1.2  beta 1 SVN-12738. Nulls are now 
displayed with "(None)". When I try and set this field to "Unknown" 
using the popup menu, and then save in the Admin, I get the following 
error: 
"This field cannot be blank." 
I get this same error when I try and add a new record in the Admin. 
I am using python 2.5.1 on Mac OS X and sqlite3. 
Change History (6)
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted | 
|---|
comment:2 by , 16 years ago
comment:3 by , 16 years ago
comment:4 by , 16 years ago
comment:5 by , 16 years ago
| Resolution: | → fixed | 
|---|---|
| Status: | new → closed | 
Between those two patches, this should now be fixed.
(In [12744]) Forced blank=True for NullBooleanField to allow it to pass model validation with a value of None. Refs #13071.