[aerogear-dev] database migration

[Daniel Bevenius]

+1 Sounds good to me.

On 7 October 2014 08:32, Christos Vasilakis <cvasilak at gmail.com> wrote:

> sounds reasonable and if it eases the pain I am +1 on it.
>
> let me know how can I help on it.
>
>
> -
> Christos
>
> On Oct 6, 2014, at 6: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
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20141007/e770037a/attachment.html