We were actually looking at liquibase and similars for this. Migrations are usually app-specific anyway, and migration from one DB type to another usually never happens.
Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 18 August 2014 16:57, Sebastian Krebs <[email protected]> wrote: > Hi, > > Actually that's more out of interest: When I use doctrine-migrations with > symfony2 "diff" generates the migrations with pure-SQL and a guard > preventing the migration to be run on an incompatible database. Is theres a > real [1] downside to rewrite the migration to use the Schema-class, that is > passed as argument anyway, so I can reuse the migration for multiple (all?) > platforms? > > Regards, > Sebastian > > [1] I know, that I can't use platform-specific functionality in that case. > That's something that can be handled seperately, when it happens :) > > -- > github.com/KingCrunch > > -- > You received this message because you are subscribed to the Google Groups > "doctrine-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/doctrine-user. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
