db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <j...@apache.org>
Subject [jira] Created: (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 16:50:46 GMT
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.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message