[DERBY-6587] Foreign Key constraint not matched when using UUID in a composite foreign key when using SYSCS_UTIL.SYSCS_IMPORT_TABLE

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.10.2.0
• Fix Version/s: 10.10.2.1, 10.11.1.1
• Component/s: SQL, Tools
• Environment: Windows 7, Java 7
• Assignee: Myrna van Lunteren
• Reporter: Pascal Grün
• Created: 27/May/14 11:41
• Updated: 09/Sep/16 09:53
• Resolved: 05/Oct/14 18:09

Description

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

Issue Links

• relates to: DERBY-6759 Derby 10.10 backport issue (fall 2014)