#29656: Range Fields do not support blank values via ModelForm
----------------------------------+--------------------------------------
Reporter: James Addison | Owner: nobody
Type: Bug | Status: closed
Component: contrib.postgres | Version: master
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by Tim Graham):
I'm not sure if there's a model field in Django where there's a chance for
two values that could be considered "empty" besides `CharField` and the
range fields. The docs for `Field.null` say, "In most cases, it’s
redundant to have two possible values for “no data;” the Django convention
is to use the empty string, not NULL." I'm not sure if there was much
consideration of null vs. empty range for range field but changing it as
this point merits a discussion on the DevelopersMailingList.
--
Ticket URL: <https://code.djangoproject.com/ticket/29656#comment:16>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.9a8c425be27414c4091b23101a653c49%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
