[forge-issues] [JBoss JIRA] (FORGEPLUGINS-54) Plugin to Database Migration Framework

Tue Oct 2 09:04:03 EDT 2012

    [ https://issues.jboss.org/browse/FORGEPLUGINS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723280#comment-12723280 ] 

darren hartford commented on FORGEPLUGINS-54:
---------------------------------------------

Potential tools/libraries that already work through database upgrades:

Liquibase - http://www.liquibase.org/, strongest, mature available tool (based on my research).  JPA or integration effort unknown. Used in Grails database migration plugin.

Flyway - http://code.google.com/p/flyway/, comparatively new, but gaining lot of traction.  Used in Spring Roo as add-on  (http://code.google.com/p/spring-roo-addon-flyway/)

There are others, however these two seem to be the strongest candidate given they already have been used in similar plugin approaches.  Personally I have had good experience with liquibase as a standalone database change tool, but never used it tightly coupled with a programming language for domain<->db change management.

flyway to liquibase comparison: http://stackoverflow.com/questions/8418814/db-migration-tool-liquibase-or-flyway

> Plugin to Database Migration Framework
> --------------------------------------
>
>                 Key: FORGEPLUGINS-54
>                 URL: https://issues.jboss.org/browse/FORGEPLUGINS-54
>             Project: Forge Plugins
>          Issue Type: Feature Request
>            Reporter: Mauro Silva
>
> Recommend idea for adding a database change plugin. The Grails plugin for database changes (http://grails.org/plugin/database-migration) may be good for inspiration, however the Forge version may not necessarily have the tightly coupled support as the Grails/Groovy domain models have, but something that supports JPA would be fabulous.
> Although a generic plugin for Liquibase or other database change management support could be useful, it would be left 'up to the developer' on how to use it which seems counter-intuitive to a more RAD-style development environment, per the specific of JPA-based data access (potentially OGM-based JPA as well).
> Usecase is for solving how to deploy database structure changes in an automated fashion to ensure the database schema does not go out of sync with the application.
> A Plugin like spring-roo-addon-flyway (http://code.google.com/p/spring-roo-addon-flyway/).
> Could be other Database Migration API that works better on Jboss ecosystem (I dont know if that is one).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira