Mailing-List: contact ddlutils-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-user@db.apache.org
Received-SPF: pass (asf.osuosl.org: domain of tomdzk@gmail.com designates
 66.249.92.198 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=WNEnFC6nyzpfh45A34Z4/jvkkb3ZyQbjDSZNQBBaDjeoAtigrIBnsIwGJYhiHaZCDG3ZjtG/XOInOW8asIkG++GQZfoCPYDpp4wGqSxKZJQB36VP2B+udZGwHTqDattAcl8Fp4+rpkEjlATc8yVWrzTfdtyjCYn/tNDAlnXvhnU=
Message-ID: <224f32340603101546wf875f6cid6d1334fbfafd26e@mail.gmail.com>
Date: Sat, 11 Mar 2006 00:46:12 +0100
From: "Thomas Dudziak" <tomdzk@gmail.com>
To: ddlutils-user@db.apache.org
Subject: Re: DdlUtils example for Derby
In-Reply-To: <44120D5C.7090008@bristowhill.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <44120D5C.7090008@bristowhill.com>

On 3/11/06, Jean T. Anderson <jta@bristowhill.com> wrote:

> Every now and then there are posts to the derby-user list about how to
> migrate databases to Derby, so I added a writeup to the Derby site on
> how to use DdlUtils to migrate databases to Derby:
>
>    http://db.apache.org/derby/integrate/db_ddlutils.html
>
> I'd appreciate any corrections or improvements you could suggest.

Thanks Jean! I just saw it on the derby-user list, and it looks great.
Just a few minor comments:

* One important thing that you should note is that the model uses only
JDBC datatypes. This is a 'limitation' which might bite a few people,
espcially when the driver is old (and for instance reports OTHER
instead of something useful) or the database has a somewhat different
type concept (such as Oracle's NUMBER type).

* Instead of using ";create=3Dtrue" you could use the createDatabase
subtask (with failOnError=3Dfalse) which has the advantage that it hides
the DB-specific details of creation.

* The database name (when writing a schema to XML) is derived from the
schema name in the db. If there is none (as for Derby), currently null
is used (which is not written to XML). I'll fix that tomorrow :-)

I'll plan on updating the website tomorrow (there have been a couple
of changes).

cheers,
Tom