Anomaly when startmigration --auto adds one and removes another model

[Erik Allik <eallik@…>]

I created an --auto migration which deleted an existing model ExistingModel and added a new model NewModel, but the weird thing is that, in the backwards method of the migration, the ExistingModel model is recreated as expected, but with field definitions referencing orm['appname.newmodel:fieldname'] instead of the expected orm['appname.existingmodel:fieldname']. Here are the relevant parts of the migration:

    def forwards(self, orm):
        db.create_table('localsite_newmodel', (
            ('id', orm['localsite.newmodel:id']),
            ('foo', orm['localsite.newmodel:foo']),
        ))
        db.send_create_signal('localsite', ['NewModel'])
        db.delete_table('localsite_oldmodel')
    
    def backwards(self, orm):
        db.delete_table('localsite_newmodel')
        db.create_table('localsite_oldmodel', (
            ('bar', orm['localsite.newmodel:bar']), # <=====
            ('id', orm['localsite.newmodel:id']),   # <=====
        ))
        db.send_create_signal('localsite', ['oldmodel'])

[andrew]

Ah, yes, this is one of those issues where the automigrator wasn't written entirely properly; I knew something like this would crop up eventually. This entire system is being rewritten as part of 0.7, so it'll be fixed there.

[ed@…]

Able to reproduce here too.

[andrew]

I can't replicate this with 0.7, so marking as fixed.