[aerogear-dev] database migration

[Matthias Wessendorf]

I have heard about FlywayDB, but from your email liquibase sounds like a
good idea!

Thanks for sharing, Erik!

On Mon, Oct 6, 2014 at 5:48 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> Now that we have 2 versions out of the door, when we change stuff we need
> an easy upgrade path. Not only for the API but also for the database.
> Because we support a couple of them having something of a process would
> help.
>
> I’ve have used liquibase in the past. You write ‘change sets’ in yaml,
> json or if you must in xml, it will create a migration table in the
> database and execute the changes needed to bring it up to date or you can
> create a sql script that will do the same. Cool thing about this approach
> is that it’s independent of the database
>
> http://www.liquibase.org
>
> Another tool I’ve heard about, but also promising is Flyway. It’s supports
> writing migrations in sql and java comes with it’s own java api. Basically
> the same idea with regards to this migration table, but here you need to
> specify your own sql scripts. Or you can write migrations in java where
> having special named java class gets executed to update/migrate the data.
>
> http://flywaydb.org
>
> WDYT?
>
> Cheers,
> Erik Jan
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/6f3f646c/attachment.html