Revision 1.0.0 of dzo is released

- At last I dared to step up to revision 1.0.0.
- Drop and recreate foreign keys, primary keys, index when
needed (for sqlserver when a column changes, for oracle when
a index that primary key is depending on is changed).
- Fixed bug when fetching metadata for columns for sqlserver.
- Add unique-constraint for oracle.
- Dont do "create table" when the table only exists implicitly (because there are reference-data or an index on the table).

The goal with 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 JBoss container, dzo has a servlet that controls the deployment process, undeploys the old application, inspects and executes the necessary database changes, and finally deploys the new application. Dzo currently works with MySQL, Oracle, and SQL Server (more to come).