You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Dag H. Wanvik (JIRA)" <ji...@apache.org> on 2014/06/05 14:36:02 UTC
[jira] [Assigned] (DERBY-6587) Foreign Key constraint not matched
when using UUID in a composite foreign key
[ https://issues.apache.org/jira/browse/DERBY-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dag H. Wanvik reassigned DERBY-6587:
------------------------------------
Assignee: Dag H. Wanvik
> Foreign Key constraint not matched when using UUID in a composite foreign key
> -----------------------------------------------------------------------------
>
> Key: DERBY-6587
> URL: https://issues.apache.org/jira/browse/DERBY-6587
> Project: Derby
> Issue Type: Bug
> Components: Store
> Affects Versions: 10.10.2.0
> Environment: Windows 7, Java 7
> Reporter: Pascal GrĂ¼n
> Assignee: Dag H. Wanvik
> Attachments: RIBulkChecker.diff, TABLE1_T.csv, TABLE2_T.csv, schema.sql
>
>
> There is a problem in org.apache.derby.impl.sql.execute.RIBulkChecker:
> result = fkCol.compare(refCol);
> if (result == 1)
> {
> return GREATER_THAN;
> }
> else if (result == -1)
> {
> return LESS_THAN;
> }
> where the JavaDoc for "compare" explicitly states that one must not use 1 or -1 to check the return value.
> The problem can be reproduced when creating a table with two fields, "UUID_FIELD char (16) for bit data" and "NUM_FIELD integer", then having a foreign key to these two fields and then using the bulk import, i.e. "CALL SYSCS_UTIL.SYSCS_IMPORT_TABLE ..."
--
This message was sent by Atlassian JIRA
(v6.2#6252)