For others getting up to speed, prior discussion is here: https://code.djangoproject.com/ticket/29656. Tim's comment from the ticket commentary is most instructive, I think:
> 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." > Given model fields: text_field = CharField(blank=True, default='') range_field = FloatRangeField(blank=True, default=NumericRange) The `CharField` (or a `TextField`) has similar parameters to the `RangeField`. For the `CharField`, a ModelForm correctly uses the default value to save '' (avoids raising an `IntegrityError`), but the RangeField does not (raises an `IntegrityError`). I'll let the team discuss; I'm not sure that I can add much else. Please correct me if/where I'm wrong. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f14af5fa-dc99-4f1a-a077-713070085e8e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
