Russell Keith-Magee <[email protected]> wrote: > Django has made a value judgement that an empty field in a form will > be interpreted as an empty string. If you don't like this default > behaviour, you can override it at the form level.
That makes sense for forms (where input is coming from the end user), but why does Django have to make this judgment on models (where input is coming from python code or has been cleaned by python code)? I too find this behaviour odd because Django is creating a default value for my model charfield when I have not specified a default. If I wanted empty string to be the default I would have put default='' in the charfield definition. -- Zach -- 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=.
