[aerogear-dev] database migration

[Stian Thorgersen]

----- Original Message -----
> From: "Matthias Wessendorf" <matzew at apache.org>
> To: "AeroGear Developer Mailing List" <aerogear-dev at lists.jboss.org>
> Sent: Tuesday, 7 October, 2014 10:58:41 AM
> Subject: Re: [aerogear-dev] database migration
> 
> 
> 
> On Tuesday, October 7, 2014, Stian Thorgersen < stian at redhat.com > wrote:
> 
> 
> I've been playing with Liquibase now and it's awesome!
> 
> That's what I'd like to use for Keycloak, but I'd also like to use the same
> as you guys do.
> 
> yes! would be great uf our projects use the same.
> 
> looks like Liquibase is the way to go?

+1

FlywayDB uses SQL directly, so we have to deal with differences between databases ourselves. IMO that renders it useless!

> 
> 
> 
> ----- Original Message -----
> > From: "Matthias Wessendorf" < matzew at apache.org >
> > To: "AeroGear Developer Mailing List" < aerogear-dev at lists.jboss.org >
> > Sent: Tuesday, 7 October, 2014 9:27:45 AM
> > Subject: Re: [aerogear-dev] database migration
> > 
> > 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
> > 
> > _______________________________________________
> > 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
> 
> --
> Sent from Gmail Mobile
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev