Main features include:

* a sensible distribution package, with source and examples
(http://code.google.com/p/dbdeploy/issues/detail?id=3)
* a change to the approach dbdeploy takes to applying changes, to
improve failure recovery
(http://code.google.com/p/dbdeploy/issues/detail?id=12)
* change of the package name to com.dbdeploy (from net.sf.dbdeploy) as
a result of the move to google code
(http://code.google.com/p/dbdeploy/issues/detail?id=13)
* a new command line interface using commons cli (this has been around
a while, but never part of an actual release)

Behind the scenes there’s been a significant refactoring of the
codebase to enable future development and to clarify dependencies.

You can download this release from
http://code.google.com/p/dbdeploy/downloads/list or from the m2
repository at http://dbdeploy.googlecode.com/svn/m2-repo/repository/.
If you’re upgrading from 2.X you should read
http://code.google.com/p/dbdeploy/wiki/UpgradingFromVersionTwo because
3.0 contains *breaking changes* including a need to change your
changelog table.

Your feedback and experiences are welcome.  Please raise or comment on
an issue, or send to http://groups.google.com/group/db-deploy-users.

Note that this is milestone release, not a final release. To see what
changes are expected before the final release of 3.0, please visit
http://code.google.com/p/dbdeploy/issues/list?q=milestone:Release3.0.

Thanks for all of your support, comments and contributions.

dbdeploy.NET represents a port of the existing java version into the .NET framework and is more geared towards inclusion in .Net projects. It currently integrates with the NAnt build tool supporting Oracle, MS SQL Server, and MySQL databases. Thanks goes out to the Thoughtworks dbdeploy.NET team (Owen Rogers, Troy Gould, Robert Norton and Tim Goodwin) who contributed to the release.

You can download v1.0 here.

We’re pleased that the judges saw value in the tool and we’re thrilled to have been recognised. Thanks again must go to ThoughtWorks and all who have contributed.

The session will cover practical approaches to database refactoring and examine how the database fits into the world of continuous integration. You won’t be surprised to hear that we’ll be demonstrating dbdeploy as one of the tools that can help.

Hope to see you there.

Winners will be announced at SD West on 17th March 2007, we’ll keep you posted…

This release was prompted by Jeff Mikres who kindly took it upon himself to write support for MySQL. Thanks Mike!

We’ve also fixed a null pointer exception bug that you would encounter if you didn’t supply a value for the undoOutputfile parameter.

You can download v2.11 here.

It can also be troublesome to find specific changes to the database within multiple migration files. Finding which migration adds a specific column can take a fair amount of time when you are working with over 50 migration files. Naming conventions can mitigate this issue some; however, naming conventions generally require that only one action occur per file. For example, the 023_create_customers_table.rb file can only create the customer table and cannot alter the purchases table to add the customer_id column. This type of naming convention helps on searching for specific changes to the database; however, it also results in a large number of migration files.

RoR’s migrations is effectively an API for creating and applying database migrations. dbdeploy’s fundamental approach is that developers should know SQL – and it does of course have the added benifit of managing the delta scripts more effectively.

The dbdeploy application is a simple solution to the problem of managing and deploying database refactorings to development, quality assurance, user acceptance testing and production environments.