I believe that this is documented. I think that it's a limitation of forms that character fields store an empty result as a null string. All the null=True means is that the model field (not the model form field) is willing to send the database a null, should it find None in the instance attribute, and that the database column has been created such that the database won't complain either. If you really need a null stored there, you will need to override form field validation or model field db preparation.
Are you sure that you need this? On Mon, Sep 20, 2010 at 10:36 AM, rihad <ri...@mail.ru> wrote: > I have these fields in a model: > ipaddr1 = models.IPAddressField() > ipaddr2 = models.IPAddressField(blank=True, null=True) > > When I "wrap" this model in a ModelForm, fill the form, and call > form.save(), empty ipaddr2 gets inserted as '', causing database > errors for Postgres' inet type. > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To post to this group, send email to django-us...@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
