#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 don't see a way forward that wouldn't be backwards incompatible. I
believe that with your proposed change, what are saving as null values
would now be saved as empty ranges. Maybe that's what some people want,
but maybe it's not. You could perhaps argue that the deficiency is the
form widget that doesn't allow distinguishing between null and an empty
range.
--
Ticket URL: <https://code.djangoproject.com/ticket/29656#comment:13>
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.e8c171f5c0b1a403087e71178b0b9f15%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
