Ticket #67 (closed defect: fixed)
--add-field for m2m fields generates invalid code
|Reported by:||eallik@…||Owned by:||andrew|
When doing startmigration appname --add-field MyModel?.field, the migration that gets generated has the following code in its backwards method:
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.