What have you tried? Django should create the migration when you swap
out the subclasses. It's mostly going to remove fields since Page is a
subclass of Displayable anyways.
There's also the nuclear option of just migrating your app back to zero
to delete the tables and just create a new migration history with the
correct parent class. Most of the time I don't mind doing this in
development because it's just dummy data anyways. However, if losing
data is not an option, you can dump the Page-based data to a fixture,
manually remove the fields you don't need, and reuse the fixture to
restore the Displayable-based model.
On 2017-09-14 4:14 PM, Andrey inte wrote:
Is there a way to migrate from Page to Displayable?
I have tried and it seems to be a pain...
--
You received this message because you are subscribed to the Google Groups "Mezzanine
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
