[ http://issues.apache.org/jira/browse/DDLUTILS-46?page=all ]
Thomas Dudziak resolved DDLUTILS-46.
------------------------------------
Resolution: Fixed
I think the problem was fixed during the re-work of the platforms. If it is
still there though, then please re-open the bug.
> 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
> Issue Type: Improvement
> Components: Core - DB2
> Reporter: Thorbjørn Ravn Andersen
> Assigned To: 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
