Database migration mechanism #114

Activity

1. rexim

   added

   kind:infrastructure

   on May 4, 2015
2. rexim

   added this to the Dropping Play framework milestone on May 4, 2015
3. ForNeVeR commented on May 7, 2015

   

   ForNeVeR

   on May 7, 2015 via email

   Member

   More actions

   I think we should also consider liquibase.
4. rexim commented on May 7, 2015

   

   rexim

   on May 7, 2015

   MemberAuthor

   More actions

   http://www.liquibase.org/
5. rexim commented on May 7, 2015

   

   rexim

   on May 7, 2015

   MemberAuthor

   More actions

   @ForNeVeR ok, I'll take a look at it when I will be implementing #115, thanks.
6. ForNeVeR commented on May 7, 2015

   

   ForNeVeR

   on May 7, 2015

   Member

   More actions

   Please note that was just a suggestion and not a complete recommendation. You should really consider both of these libraries and use the best of them. They have some differences. In particular:

   • liquibase tends to be more model-centric and can operate with entities such as table or column, while all Flyway does is execute raw SQL scripts;
   • liquibase also can wrap every migration in transaction (if there is transactional DDL support in database) and I am not sure whether Flyway can do this;
   • at last, Flyway have a command to clean the database that is highly valuable in tests, and I am not aware whether liquibase have such function.
7. rexim commented on May 7, 2015

   

   rexim

   on May 7, 2015

   MemberAuthor

   More actions

   @ForNeVeR this issue was created only for suggestions. So I don't know why I would treat anything differently in here.

   Anyway, thanks for the comparison!