Migrating plata on an existing database fails about plata HOT 4 CLOSED

Hi Henning

That's a known problem, and I'm not sure how this should be solved. We're emulating a lazy foreign key with the PLATA_SHOP_PRODUCT setting, something which isn't really supported by Django (and therefore not supported by South either).

I'm using the simple example to create the migrations, unfortunately this means that products in all other apps will lead to the errors you're seeing.

I'm a bit stumped how we can provide migrations in Plata itself and still support PLATA_SHOP_PRODUCT.

Your fix is certainly correct but involves handiwork, something which I'd like to avoid if possible at all.

Thanks,
Matthias

from plata.

So maybe including migrations wasn't such a good idea after all.

I'm thinking that the best way forward might be to remove the migrations, and provide instructions in the release notes how migrations could be generated if necessary.

Opinions?

from plata.

I for one vouch for not having migrations, just because "simpler is better"

from plata.

One argument against migrations would be that the final Product model is configurable and hence not suitable for migrations. So I'd prefer some kind of documentation that explains how to activate (and maintain) migrations for a distinct Plata installation.

from plata.