Changing a ForeignKey from a "real" model to a proxy of it generates invalid migration code

[Ulrich Petri <mail@…>]

Steps to reproduce:

1) Have a model with a ForiegnKey? to e.g. auth.User
2) create & run migration
3) Add a ProxyModel? of auth.User (in my example "FilerUser?")
4) try to create migration (nothing to be done)
5) Change ForiegnKey? on first Model to use the Proxy
6) create migration - invalid python code results (see below)

class Migration(SchemaMigration):

    def forwards(self, orm):
        
        # Adding model 'FilerUser'
        db.create_table('auth_user', (
            ,
        ))
        db.send_create_signal('filer', ['FilerUser'])


    def backwards(self, orm):
        
        # Deleting model 'FilerUser'
        db.delete_table('auth_user')

Even worse than the broken forwards migration is the backwards one which would delete the base of the proxy model.

[andrew]

This is probably related to #423, but doing a different operation.

[Ulrich Petri <mail@…>]

I have to correct my report: actually I have a ManyToMany? field not a ForeignKey?.