db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Commented: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts
Date Tue, 11 Mar 2008 17:37:04 GMT
Does SQL standard or Derby documentation actually document the specific 
number we return for any of these error conditions?  For Derby 
documentation I mean separate from the document which lists all errors, 
ie. does create index documentation say what error number you will get 
for a given error.

It does seem like the best case would be for the error message system to
somehow return a different error message for the same number if it is
in soft upgrade vs. hard upgrade.  Does the error message system support
such a thing?

Kathey Marsden (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12577517#action_12577517
] 
> 
> Kathey Marsden commented on DERBY-3523:
> ---------------------------------------
> 
> I see examples in messages.xml, such as 8006 where we have more than one instance of
a message with the same SQLState but different messages.   Is that a possibility.
> 
> 
>> sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated
with wrong message texts 
>> ------------------------------------------------------------------------------------------------------------------
>>
>>                 Key: DERBY-3523
>>                 URL: https://issues.apache.org/jira/browse/DERBY-3523
>>             Project: Derby
>>          Issue Type: Bug
>>    Affects Versions: 10.4.0.0, 10.5.0.0
>>            Reporter: Anurag Shekhar
>>            Assignee: Anurag Shekhar
>>
>> 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.
> 


Mime
View raw message