Spaces in model field definition params cause sqlite errors

[Scot Hacker]

With this class definition:

class MyModel(models.Model):

title = models.CharField(blank=True, null=True, max_length=60)

run syncdb against sqlite. The title column will end up in sqlite defined as a required field (it shouldn't be). Remove the sqlite file, and change the model slightly:

class MyModel(models.Model):

title = models.CharField(blank=True,null=True,max_length=60)

(remove the spaces between the field options). syncdb again and the column now correctly is non-required.

The presence of the space(s) between field options seems to be significant.

[Anssi Kääriäinen]

There is something else going on. If the spaces were significant, it would mean there was a huge showstopper bug in Python. The spaces are not seen by Django at all, they are parsed by Python itself. Basically every Python project would be broken.

Closing as invalid.

[Scot Hacker]

Hmm. I should have noted that I also tested this against mysql, and did not have a problem. It was only sqlite3 (on OS X Lion) that demonstrated the problem. I'll see if I can someone else to reproduce it on a different codebase and machine.