[forge-issues] [JBoss JIRA] (FORGE-694) JPA database refactor management (liquibase, etc)

[darren hartford (JIRA)]

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

darren hartford commented on FORGE-694:
---------------------------------------

Did not see prior description (searched for keywords like liquibase returned nothing, and searching database I may have only searched Forge and not Forge Plugins).

However, Flyway is another growing-in-popularity database change management approach.  I know some liquibase capabilities may not necessarily exist for Flyway, but may not be relevant for certain scenarios (for example, I believe liquibase allows direct DBA-style sql statements for things like custom data migration efforts during the automated upgrade process, and already handles parallel deploys by preventing more than one app deploy to upgrade the database schema (app cluster scenarios)).

                
> JPA database refactor management (liquibase, etc)
> -------------------------------------------------
>
>                 Key: FORGE-694
>                 URL: https://issues.jboss.org/browse/FORGE-694
>             Project: Forge
>          Issue Type: Feature Request
>          Components: Brainstorming
>         Environment: JPA-based projects
>            Reporter: darren hartford
>            Priority: Critical
>              Labels: hibernate, jpa, refactoring
>
> 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.

--
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