South deletes table that has: managed = False

[astraforever@…]

in class Meta for one of my models I have:
managed = False

when I run startmigration .. --auto and then migrate, south deletes the table of this model from the database!

[andrew]

Did you use south to create the model, and _then_ add managed=False? That would look to South's internals like you'd removed the model, and so it would try to delete it.

[astraforever@…]

No I didn't use south to create the model.
I used the sql script in the database to paste the table.

Besides south tries to delete this table with every next migration (with --auto), though it has already deleted it in previous migration.

[andrew]

Alright, I'll see if I can replicate it.

[gvangool]

Just my 2 cents, South also tries to create a Model which has managed = False .

[vasily.ivanov@…]

same issue here

./manage.py convert_to_south creates db.create_table and db.delete_table statements for managed=False models

[andrew]

Fixed in [516b011fe68c].

[vinuta@…]

I am using South 0.7.3 but I still see this problem. If this is fixed how do I tell South to not use models with managed=False

[andrew]

I would start by using the latest release, 0.7.4, and then if that doesn't work, open a new bug report containing a full traceback, your models file, and other code samples that might be needed.

[shai@…]

I just reviewed the code, and it seems that while the problem is solved for adding/deleting tables, it is not solved for changing tables (which is the case where I've just run into it).

I'll try to provide a test and fix.

[shai@…]

Fixed in [198275dac219].

[anonymous]

Replying to shai@…:

Fixed in [198275dac219].

Has this change been put into a published version of South yet? If not, when might that happen.

[andrew]

It's in 0.7.5.