Comments on: Grails and LiquiBase – How to use

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.

By: maxou

maxou — Tue, 18 May 2010 07:25:26 +0000

Hi,

Thanks for the tutorial !
But, there is one thing that I am not sure to have understood. In fact, the changelog.xml is not generated with domain classes but with the database or with informations writen manually. We can’t generate this file with domain classes ?

Thanks,

maxou

By: Masiar

Masiar — Wed, 29 Jul 2009 13:52:24 +0000

Hi jakob,

nice post. Could you publish the mentioned compareToChangelog ? It would be helpful!!

thanks,
masiar

By: Mark

Mark — Mon, 29 Jun 2009 21:29:11 +0000

I recently wrote a JDBC driver wrapper to perform schema management. Basically what you do is setup your jdbc URL to use the wrapper around your backend JDBC driver and in doing so deployment will occur automatically prior to the release of the first client connection. This solution works with LiquiBase, Grails, plain old Java, and/or any tool that uses JDBC.

The driver currently the LiquiBase schema manager in addition to a more direct internal schema manager. This gives the user choice since LiquiBase provides database independence via the XML layer and for users who must support more then one DB type using LiquiBase as the schema manger is the best approach. The standard manager is the best approach for a shop that uses only one type of DB and wants to take advantage of driver level features for schema record and/or use vendor specific SQL statements rather then the XML indirection model.

In any case please checkout the project on my blog.
http://markfarnsworth.wordpress.com/2009/06/27/garin/

By: adwin

adwin — Thu, 11 Jun 2009 02:00:11 +0000

thanks for the tutorial. it really helpfull …

i am using autobase before (in grails 1.0.4) and now move to use liquibase (in grails 1.1.1) since the autobase plugin are not working

By: jakob.kuelzer

jakob.kuelzer — Thu, 09 Oct 2008 12:52:12 +0000

The db-diff command just ouputs the changes to the console and usually this is what you want. You can review the changes, copy it into your changelog file or just use it to see if there are differences.

Cheers,
Jakob

By: Dimitri

Dimitri — Thu, 09 Oct 2008 09:11:28 +0000

Is the db-diff command supposed to add diff’s to changelog or do you just copy it from the std-out? Nice post well done!

By: เกรลส์ หกสิบหก » Grails Podcast Episode 67

เกรลส์ หกสิบหก » Grails Podcast Episode 67 — Mon, 29 Sep 2008 17:22:26 +0000

[...] 1. Grails Plugin ซึ่งประกอบไปด้วย – P6Spy Plugin สำหรับ monitor JDBC queries – Grails Debug Help Plugin – Grails Mail Plugin 0.4 Released – Grails Testing Plugin 0.2 Released – EasyB Grails Plugin – การใช้งาน Grails LiquiBase Plugin [...]

By: Groovy on Grails : Grails Podcast Episode 67: Newscast for September 27 2008 (Sven Haiges & Glen Smith)

Sun, 28 Sep 2008 20:20:19 +0000

[...] Using the Grails LiquiBase Plugin Blog Post [...]