You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-dev@db.apache.org by "Thomas Dudziak (JIRA)" <ji...@apache.org> on 2006/07/13 08:48:34 UTC
[jira] Commented: (DDLUTILS-46) Schemas dumped from DB2/400 tries
twice to create primary key when loaded to Derby
[ http://issues.apache.org/jira/browse/DDLUTILS-46?page=comments#action_12420800 ]
Thomas Dudziak commented on DDLUTILS-46:
----------------------------------------
Could you try that again with the current SVN source ? The problem is that DdlUtils has to manually filter the unique indexes that the database maintains automatically for the primary keys (the JDBC driver does not filter them). And for some databases it is not easy to determine this.
> Schemas dumped from DB2/400 tries twice to create primary key when loaded to Derby
> ----------------------------------------------------------------------------------
>
> Key: DDLUTILS-46
> URL: http://issues.apache.org/jira/browse/DDLUTILS-46
> Project: DdlUtils
> Type: Improvement
> Reporter: Thorbjørn Ravn Andersen
> Assignee: Thomas Dudziak
> Priority: Minor
> Fix For: 1.0
>
> I dump a schema from a DB2/400 machine. All tables which have a primary key also lists the primary key as a unique index:
> <unique name="TBLACCESSMODULE">
> <unique-column name="ID"/>
> </unique>
> When the schema is loaded into Oracle, Oracle complains when trying to make the index, with an error (cannot reproduce right now) to the effect that the unique index does already exist. Presumably because the primary key was created along with the table.
> Perhaps PK's should be filterered out from the unique indexes?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira