db-ddlutils-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Dudziak" <tom...@gmail.com>
Subject Re: Some bugs with Oracle
Date Thu, 23 Feb 2006 10:19:08 GMT
On 2/23/06, Hans Muñoz <Hans.munoz@digibis.com> wrote:

> I think the problem is in the method removeInternalPrimaryKeyIndex as long
> as it only have one line... return false; so it can never remove the
> duplicate index.
> The original Database hasn't been created with ddlUtils, the SQL definition
> of one table is:


I'll look into it.

> Well sure not a smart and standard way :).
> In oracle you can get info about triggers and sequences from user_sequences
> and user_triggers tables, this can be usefull but will only work with
> Oracle. From here, the rest still not easy, the easy and bad solution is to
> make it only work with databases created with ddlutils checking (while
> looking for changes) the names of triggers/sequences?.

Oracle-only is not the problem (that's why there are the platform
classes). The point is that DdlUtils should determine whether the
trigger and sequence are for auto-increment. Esp. whether the
sequence/procedure sets the values of columns. And that is the hard


View raw message