[DERBY-3523] sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.4.1.3, 10.5.1.1
• Component/s: SQL
• Labels: derby_triage10_5_2
• Urgency: Low
• Assignee: Unassigned
• Reporter: Anurag Aggarwal
• Created: 11/Mar/08 16:50
• Updated: 15/Feb/11 21:09

Description

There are three messages which after Derby-3330 checkin now giving wrong information. These are

42831:'

{0}' cannot be a column of a primary key or unique key because it can contain null values.
42Z20:Column '{0}

' cannot be made nullable. It is part of a primary key or unique constraint, which cannot have any null able columns.
X0Y63.S:The command on table '

{0}

' failed because null data was found in the primary key or unique constraint/index column(s). All columns in a primary or unique index key must not be null.

Issue Links

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