db-ddlutils-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thorbjørn Ravn Andersen (JIRA) <j...@apache.org>
Subject [jira] Commented: (DDLUTILS-46) Schemas dumped from DB2/400 tries twice to create primary key when loaded to Oracle
Date Thu, 10 Nov 2005 08:48:03 GMT
    [ http://issues.apache.org/jira/browse/DDLUTILS-46?page=comments#action_12357202 ] 

Thorbjørn Ravn Andersen commented on DDLUTILS-46:
-------------------------------------------------

I got that wrong.  The target database in this bug report is Derby, not Oracle.

> Schemas dumped from DB2/400 tries twice to create primary key when loaded to Oracle
> -----------------------------------------------------------------------------------
>
>          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

>
> 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


Mime
View raw message