On Thu, Feb 3, 2011 at 4:55 PM, Richard Laager <[email protected]> wrote:
> On Thu, 2011-02-03 at 13:46 -0500, Tobias McNulty wrote: > > the behavior of all fields, except for BooleanField, is to default to > > the empty value supported by that field. > ... > > On the other hand, False is in no way an "empty value." > > From the point of view of the model layer, your point makes sense. > However, I think the UI is the challenge. This would force every > BooleanField to have a drop-down (like NullBooleanField) instead of a > checkbox, at least on the /add/ forms. > > No, that problem is already handled by the CheckboxInput widget ( http://docs.djangoproject.com/en/dev/topics/db/models/#field-name-hiding-is-not-permitted), which forces "no value" to False. We're not relying on the model-level False default to get check boxes to work properly. Karen -- http://tracey.org/kmt/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
