On Mon, Jan 26, 2015 at 11:43 AM, Douglas Campos <qmx(a)qmx.me> wrote:
Howdy!
I've been envisioning a plan for UPS migrations, and would like to get
some feedback from the community, so here it is:
When there are model changes, it's kinda annoying to generate the sql
migration files. This is one of the reasons Erik Jan de Wit started
working to add liquibase to the project, allowing for seamless
migrations.
I'd like to build upon Erik's initial work and prepare a `ups-migrator`
distribution:
ups-migrator-VERSION.zip
`--ups-migrator.jar
`--ups-migrator-postgresql.properties
`--ups-migrator-mysql.properties
`--lib
`-- <jdbc drivers>
`-- <liquibase & deps>
This migrator tool can be run with plain `java -jar` and deals with all
the migrations needed up to `VERSION`, which means we would need only
one migrator tool for both 1.0.x and HEAD.
Sounds like a great idea. How do I specify the actual DB that I'd like to
touch during the migration? Do I specify (cmd args?) which of the
properties is picked up ?
-Matthias
Thoughts? Comments?
--
qmx
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
sessions:
http://www.slideshare.net/mwessendorf
twitter:
http://twitter.com/mwessendorf