Comments on: Grails and LiquiBase – How to use

By: Working with the Grails Database Migration Plugin | Tomás Lin’s Programming Brain Dump

Fri, 24 Jun 2011 08:45:44 +0000

[...] changesets, we use the database diff mechanism provided by the plugin. This is very similar to the liquibase mechanism described here by Jakob Kultzer, but made easier due to the Database Migration plugin’s [...]

By: Jakob Külzer

Jakob Külzer — Tue, 10 May 2011 03:48:20 +0000

Hello Imran,
thank you, I’m glad my post is so useful to you.

By: Imran

Imran — Mon, 09 May 2011 06:17:15 +0000

Hey Jakob. You have done a great job by writing this article and simplifying the database change management through liquibase. I keep on referring to this article every now and then, especially the section, “Using LiquiBase in the Middle of a Project”. Thanks.

By: Jakob Külzer

Jakob Külzer — Fri, 03 Dec 2010 04:24:58 +0000

Hey Justin,
that is indeed something I’ve been thinking about for a while. You can use liquibase to do that, using the insert data (http://www.liquibase.org/manual/insert_data) or load data (http://www.liquibase.org/manual/load_data) refactorings. You could also use custom sql refactoring (http://www.liquibase.org/manual/custom_sql_file) depending on your needs. I have to admit that I never used these refactorings, though.

The obvious drawback is that loading data via these mechanisms doesn’t offer a rollback. An interesting question is whether this could be part of an automated database synchronization mechanism… hmmm…

Your question actually made me look at the new refactorings — letting me solve some other problems elegantly now. Thanks.

By: Justin

Justin — Wed, 01 Dec 2010 19:27:08 +0000

Great post!

I am wondering if the grails liquibase plugin can support row data as well as schema changes. I have created a new table and want it populated with data when I perform the migration. Is there some other mechanism other than manually creating a data-load script and applying it to all my databases.

Thanks.

By: Grails Liquibase plugin: dbDiff tool workaround « Intelligrape Groovy & Grails Blogs

Tue, 12 Oct 2010 12:07:39 +0000

[...] found one great article by Jackob Kulzer. As explained by Jackob Kulzer, dbDiff tool in the plugin is hard coded to compare development and [...]

By: Amit Jain

Amit Jain — Tue, 12 Oct 2010 10:12:41 +0000

Thanks a lot!! Nice post!!

By: Blog bookmarks 08/19/2010 « My Diigo bookmarks

Blog bookmarks 08/19/2010 « My Diigo bookmarks — Thu, 19 Aug 2010 04:34:37 +0000

[...] Grails and LiquiBase – How to use « Jakob Külzer [...]

By: maxou

maxou — Tue, 25 May 2010 13:05:33 +0000

Ok, I had time to test the tool.

In fact, the command which is very cool is db-diff (generate changelog is not very necessary in fact, db-diff do better). You don’t have to write by hand the xml code. You just have copy and paste.
On the other hand, it’s weird that the diff is done between dev and test databases. Why not between dev and prod databases ?
So, I had put the production database in the test environnement. I do : “grails test migrate”.

With a Db-diff which work correctly, Autobase not have reasons to exist.

My only problem is with foreign keys of the framework tables (fmwk_item…) which it searches to create and drop in every db-diff.

By: Jakob Külzer

Jakob Külzer — Tue, 18 May 2010 21:16:33 +0000

@maxou: there’s two ways you can generate your changelog. You can either write it manually or you can get liquibase to generate it for you. The later will take a certain existing database structure and create your changelog.xml from it. To answer your question, no, you cannot generate a changelog.xml directly from domain classes (because this is highly database dependent). But you can get Grails and hbm2ddl to populate a database for you and then use liquibase to create the changelog.xml.