#24674 closed Bug (fixed)
NullBooleanField in a model is converted to NullBooleanField in a form, not CharField
| Reported by: | Marten Kenbeek | Owned by: | Simon Charette |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
The documentation[1] states that a NullBooleanField on a model is converted to a CharField when using a ModelForm. It is actually converted to a NullBooleanField [2].
[1] https://docs.djangoproject.com/en/1.8/topics/forms/modelforms/#field-types
[2] https://github.com/django/django/blob/stable/1.8.x/django/db/models/fields/__init__.py#L2080
Change History (5)
comment:1 by , 11 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Version: | 1.8 → master |
comment:2 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
In 37e23c60: