Hi Niels, Mezzanine does come with built-in migrations; pages <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/pages/migrations>, blog <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/blog/migrations>, core <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/core/migrations>, forms <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/forms/migrations>, and gallery <https://github.com/stephenmcd/mezzanine/tree/master/mezzanine/gallery/migrations> should interest you.
-ken On Sun, Sep 13, 2015 at 10:27 AM, Niels Jakob Buch <[email protected]> wrote: > That explains the need for the first app-specific migrations. > > What about mezzanine, does it come with built-in migrations. > > On Sun, Sep 13, 2015 at 3:48 PM, Eduardo Rivas <[email protected]> > wrote: > >> I think Django wouldn't know how to create your application's tables >> without the migration files. Migrations are required with every concrete >> model in Django 1.7 and up. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Mezzanine Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/mezzanine-users/x6oxLhpK7Io/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
