South fails to add a blank=True/null=False field without manually adding default value

[Erik Allik]

For example, adding:

my_field = models.CharField(max_length=255, blank=True)

should assume a default value of "", but currently running

db.add_column('myapp_mymodel', 'my_field', models.CharField(max_length=255, blank=True))

gives

psycopg2.IntegrityError: column "my_field" contains null values

...at least on PostgreSQL 8.3, that is.

Not a blocker, but annoyance nevertheless. Using SVN r258.

[andrew]

Not a blocker, but indeed annoying - still, somewhat matches my expectations. Bumping to 0.7.

[mbarto]

If the field allows empty strings (which CharFields? do) we will manually add the default as empty string "", and at the same time throw ValueError? to avoid this behavior for fields without the ability to allow empty strings (ie. IntegerFields?).

[smcoll]

i got this same error with a TextField?(blank=True) using 0.6.2. Shouldn't a TextField? have the same behavior as a CharField??

[andrew]

It probably should do, yes; I'm not sure why it isn't. Could you open a new ticket for this, with information about what database and Django you're using?

[anonymous]

I don't think this is minor. Adding a blank CharField? or TextField? is one of the simplest, most common use cases, and often the first thing you try with South. This bug--which is in the current stable version--means South throws an exception and fails in that extemely common case.

[andrew]

This issue is fixed in the upcoming development release of South, so there's no need to re-open it.

Also, for the record, many people do add CharFields? and TextFields? all the time, and they work (the issue in 0.6.2 only affects certain combinations of DBMSen and field options, and as I said, is now fixed in trunk).

[impomiaideada]

Thank You For This Blog, was added to my bookmarks.