October 2012 - forge-issues - Jboss List Archives

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

by darren hartford (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-54?page=com.atlassian.jira.p... ] darren hartford commented on FORGEPLUGINS-54: --------------------------------------------- Feature *wish* list (starting with what would be desireable versus achievable): *Bi-directional Incremental change support. I do not recall where, but this was a black eye for Forge/Hibernate reverse engineering in one review ('destructive' was a word used to describe it, which is unfair when you talk reverse … [View More]engineering tool versus change management tool) when compared to Grails and Roo. --change in database schema and have 'incremental' change support to domain code...without replacing existing code (example, if you modified the JPA design to include TABLE_PER_CLASS inheritance, and you add a new column to one of those tables or a separate class that as one-to-many to that inheritance, do not want to loose that work). --change the domain in code, incrementally handle db migration. Note that column renames need to be specifically addressed, and some type of ability to *track* other columns marked for deletion, but not actually purge unless explicitly defined. *SQL support to handle more database-specific work, like data migration work (if merging or breaking apart data in column(s) to other column(s)). *SQL specific schema support -- Specifically, there may be additional columns/relations in the table design that do not/are not part of the domain model. This should be supported with some type of 'ignore' feature when working on the code-domain but still exist/support/be upgraded as part of the upgrade process (new/improved indexes, constraints, spoc/functions, sql views for example). Not primary feature of this plugin, but should support it. > 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 [View Less]

12 years, 5 months

1
0
0 / 0

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

by darren hartford (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-54?page=com.atlassian.jira.p... ] 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 … [View More]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... > 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 [View Less]

12 years, 5 months

1
0
0 / 0

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

by darren hartford (JIRA)

darren hartford created FORGE-694: ------------------------------------- Summary: 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 Recommend idea for adding a database change … [View More]

12 years, 5 months

2
5
0 / 0

[JBoss JIRA] (FORGE-610) ejb plugin: provide creation funzionatlity

by fiorenzo pizza (JIRA)

fiorenzo pizza created FORGE-610: ------------------------------------ Summary: ejb plugin: provide creation funzionatlity Key: FORGE-610 URL: https://issues.jboss.org/browse/FORGE-610 Project: Forge Issue Type: Enhancement Reporter: fiorenzo pizza it should be useful to add the ejb plugin a creation ejb new-ejb --type SINGLETON|STATELESS|STATEFUL --named TestEJB jms new-mdb --destinationType QUEUE|TOPIC --… [View More]

12 years, 5 months

4
9
0 / 0

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

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGEPLUGINS-54?page=com.atlassian.jira.p... ] George Gastaldi updated FORGEPLUGINS-54: ---------------------------------------- Description: 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 … [View More]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). was: A Plugin like spring-roo-addon-flyway (http://code.google.com/p/spring-roo-addon-flyway/). Culd be other Database Migration API that works better on Jboss ecosystem (I dont know if that is one). > 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 [View Less]

12 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues October 2012