tobami/codespeed — Issue #91: Missing migration for Revision.project null=True
Author: squiddy
Created: 2011-12-03 16:33:55+00:00
State: open

I was going to work on #35, but when I wanted to create a new migration, south found another change:

```
$ python manage.py schemamigration codespeed --auto
? The field 'Revision.project' does not have a default specified, yet is NOT NULL.
? Since you are making this field nullable, you MUST specify a default
? value to use for existing rows. Would you like to:
? 1. Quit now, and add a default to the field in models.py
? 2. Specify a one-off value to use for existing columns now
? 3. Disable the backwards migration by raising an exception.
```

In 6cefd8e1a4c275c5c4cc5d2f0c14a7c66865c5b9 `null=True` was added to the definition of `Revision.project`, but apparently no migration was added.

If I'm not mistaken, each revision has a link to a project (a revision belongs to a branch, and that branch belongs to a project). Why can `project` be left out on a revision then?