My vote is for using xml, not sql, for the ddl. For example, have a look at Apache DDLUtils (which I feel isn't as well known as it ought to be).
It's really nice to have just one ddl which works across multiple vendors when
you want to make sure your stuff works on Postgres, SQL Server,
Geoffrey:
I haven't used Liquibase, so I'm not the best person to highlight all of the
differences between the two projects. Like some other folks on this list, I
only learned about Liquibase a few weeks ago (and haven't tried it out
yet). However, there are a few notable differences as far as
On Mon, Mar 9, 2009 at 10:38 PM, Christian Nelson cnel...@slac.com wrote:
The db-migration-maven-plugin
http://code.google.com/p/c5-db-migration/provides support for
managing project database structure changes over time
(a la rails migrations). Each change is captured as a discrete migration
This is the first I've ever heard of LiquiBase; according to the archives
there's only one other email from October 2008 that mentions it.
It seems to me that there ought to be better marketing for maven and its
plugins; see, for example, the huge list of eclipse plugins that you can get to
On Tue, Mar 10, 2009 at 4:33 PM, Rusty Wright rusty.wri...@gmail.comwrote:
This is the first I've ever heard of LiquiBase; according to the archives
there's only one other email from October 2008 that mentions it.
It seems to me that there ought to be better marketing for maven and its
Yeah, I just wanted to carp because there are so many reasons to use maven but
no easy way to find out why.
Geoffrey Wiseman wrote:
On Tue, Mar 10, 2009 at 4:33 PM, Rusty Wright rusty.wri...@gmail.comwrote:
This is the first I've ever heard of LiquiBase; according to the archives
there's
