The goal of dzo is to treat application database objects the same way the application's source code is treated, with respect to development, revision control, and deployment. Dzo uses a text file that contains native create statements for all database objects and compares them against the actual database-schema. As a result, dzo creates the SQL statements needed to update the database schema (or you can let dzo execute the SQL statements directly). If your application lives in a Tomcat or Java EE application server, dzo has a servlet that controls the deployment process, inspects and executes the necessary database changes, and finally deploys the application. Dzo currently works with HSQLDB, MySQL, Oracle, PostgreSQL, and SQL Server (more to come).
In this version, the old tomcat deployment Webapp is removed. The deprecated element <dzoSchema> has been removed from ant. Persistence annotations have been added (@@Annotation). A bug has been fixed when fetching code for functions/procedures/triggers/packages in Oracle. Drop and recreate foreign keys when something changes. A bug when fetching metadata for a specific primary key in Oracle has been fixed. Support has been added for "alter table XXX add constraint ...", so dzo can use ddl generated from other tools. Support has been added for PostgreSQL 9.1.