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] Updated: (DERBY-3523) sql states (X0Y63, X0Y63, X0Y63.S) related to nulls in unique constraints are associated with wrong message texts
Date Thu, 27 Mar 2008 10:07:24 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anurag Shekhar updated DERBY-3523:
----------------------------------

    Attachment: derby-3523-upgradetest_v2.diff

In Derby 10.0 the syntax for creating primary key along with table creation was 

create table t1 (i integer not null primary key)

in latter version not null wasn't mandatory. In my previous patch there was no 'not null'
and thats why there were failure. 
I had tested it with upgrades from 10.3 only. Sorry for the trouble.

In my new patch I have added 'not null; in create table statement and also checking if the
version is at least 10.2 while trying "alter table alter column i null" as this was not 
available in 10.2. 

I have tested upgrade tests with following version in release directory

10.0.2.1 
10.1.1.0  
10.1.2.1  
10.1.3.1 
10.2.1.6  
10.2.2.0  
10.3.1.4  
10.3.2.1

> 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
>         Attachments: derby-3523-upgradetest.diff, derby-3523-upgradetest_v2.diff, derby-3523v1.diff,
derby-3523v2.diff, derby-3523v3.diff
>
>
> 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