Blank form fields are not accepted

Question

Table in PostgreSQL database:

CREATE TABLE pmss_recordmodel
(
  id serial NOT NULL,
  "Name" character varying(100),
  CONSTRAINT pmss_recordmodel_pkey PRIMARY KEY (id)
)
WITH (OIDS=FALSE);
ALTER TABLE pmss_recordmodel OWNER TO postgres;

Model:

class RecordModel(models.Model):

    def __unicode__(self):
        return self.Name

    Name = models.CharField(max_length = 100, unique = False, null = True, blank = True)

When I POST data with blank Name field, form.is_valid() returns False. Why? Am I missing something?

EDIT:

class RecordForm(forms.ModelForm):

    class Meta:
        model = RecordModel

    Name = forms.CharField(label = "Имя ", widget = forms.TextInput(attrs = {'size': 15}))

{'Name': [u'\u041e\u0431\u044f\u0437\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0435 \u043f\u043e\u043b\u0435.']} ({'Name': ['required field']}) — DSblizzard, Feb 07 '12 at 02:32
Partial solution: http://stackoverflow.com/questions/1134667/django-required-field-in-model-form — DSblizzard, Feb 07 '12 at 02:40

score 1 · Accepted Answer · answered Feb 07 '12 at 09:31

1

Django forms documentation:

By default, each Field class assumes the value is required

Set the "required" argument to False as such:

Name = forms.CharField(required = False, label = "Имя ", widget = forms.TextInput(attrs = {'size': 15}))

answered Feb 07 '12 at 09:31

jpic

32,891
5
112
113

score 0 · Answer 2 · answered Feb 07 '12 at 17:56

You could be having problems with how the field is defined in your database.

This seems like it could be the common situation of doing syncdb with the field initially not having blank=True null=True and then adding those terms later (after initial syncdb) to make the field not required. These settings will not be applied by simply running syncdb again. It requires a database migration or a database flush (will clear existing data, which isn't necessarily bad in development).

Blank form fields are not accepted

2 Answers2