--add-field for m2m fields generates invalid code

[eallik@…]

When doing startmigration appname --add-field MyModel?.field, the migration that gets generated has the following code in its backwards method:

db.delete_column('myapp_mymodel', 'field')

which is invalid because 'field' is not an actual field in the database. The command should either generate working code, or the semantics of db.delete_column could be changed to accommodate this behavior.

[andrew]

Fixed in [122]. (The forwards side was also useless, since you need to manually create tables).

Also, note one of the answers in the FAQ; if you're using through=, then use --model, not --add-field.