[DERBY-991] Defining the same primary key twice on a table actually attempts to create two constraints.

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6
• Component/s: SQL
• Labels: derby_triage10_5_2
• Urgency: Normal
• Issue & fix info: Newcomer, Repro attached
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 15/Feb/06 23:28
• Updated: 15/Feb/11 21:08

Description

Defining the same primary key twice on a table actually attempts to create two constraints.

ij> create table t ( i int, b int, primary key (i,b), primary key (i,b));
ERROR 42Z93: Constraints 'SQL060215062628851' and 'SQL060215062628850' have the
same set of columns, which is not allowed.

ij> create table t ( i int primary key primary key primary key);
ERROR 42Z93: Constraints 'SQL060214082337951' and 'SQL060214082337950' have the
same set of columns, which is not allowed.

Other combinations of two primary keys (that I could think of) return the correct error.

ij> create table t ( i int, b int, primary key (i,b), primary key (b));
ERROR 42X90: More than one primary key constraint specified for table 'T'.
ij> create table t ( i int primary key, b int primary key);
ERROR 42X90: More than one primary key constraint specified for table 'T'.

Issue Links

• is related to: DERBY-789 Usability issue: "Constraints have the same set of columns"
• relates to: DERBY-3300 CREATE INDEX that matches an existing index succeeds with a 01504 warning but does not create the index.