Augustin's correct :) If I could suggest a solution, I would like to have a `null=False` argument on form fields. I believe this would fix the problems noted above and be sort of backwards-compatible. When using model forms, the argument would be set according to the `null` attribute of the respective model field.
Other version of this is a argument like `empty_value=''` which would allow more variability, though I'm not sure if it's needed. I am not quite sure if there are completely unrelated places where Django uses hardcoded empty string as a empty value. That would be a problem. What do you think? Vlastimil Dne čtvrtek, 7. listopadu 2013 13:55:54 UTC+1 Karen Tracey napsal(a): > > On Thu, Nov 7, 2013 at 5:37 AM, Vlastimil Zíma <[email protected]<javascript:> > > wrote: > >> I don't want to enforce anybody to use only NULL as empty value, I just >> want Django to store NULL in database when I told it to. And I don't mean >> the way of overriding all the form fields as I have to now. >> > > A concrete proposal would help here. > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/9549bec7-ae13-43c2-9b58-b02177897e87%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
