[DERBY-3502] Unique Constraint's backing index when shared with existing indexes doesn't behave as expected

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 10.4.1.3
• Fix Version/s: 10.4.1.3
• Component/s: SQL
• Assignee: Anurag Aggarwal
• Reporter: Anurag Aggarwal
• Created: 06/Mar/08 14:07
• Updated: 24/Mar/08 08:28
• Resolved: 24/Mar/08 08:27

Description

Unique Constraint now uses non unique backing indexes with new attribute UniqueWithDuplicateNulls. This index has following sharing properties

1. Can use an existing unique index.
2. Non Unique indexes (and foreign key) can use this index.

While dropping a unique index a new index for unique constraint should be created.
when a unique constraint is dropped a new index for a non unique index or foreign key should be created.

Army has found several issues in actual behavior. This problems are listed in DERBY-3456.

Issue Links

• is related to: DERBY-3330 provide support for unique constraint over keys that include one or more nullable columns.