Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1222317281.1206525565964.JavaMail.jira@brutus>
Date: Wed, 26 Mar 2008 02:59:25 -0700 (PDT)
From: "Anurag Shekhar (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-3566) Alter column set data type not
 allowed in soft upgrade with unique constraint
In-Reply-To: <1049367707.1206375324604.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anurag Shekhar reassigned DERBY-3566:
-------------------------------------

    Assignee: Anurag Shekhar

> Alter column set data type not allowed in soft upgrade with unique constraint
> -----------------------------------------------------------------------------
>
>                 Key: DERBY-3566
>                 URL: https://issues.apache.org/jira/browse/DERBY-3566
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.4.0.0
>            Reporter: Kathey Marsden
>            Assignee: Anurag Shekhar
>            Priority: Minor
>
> In 10.3 I can do this:
> ij> create table t0 (i int not null, v varchar(1) not null, constraint  uq unique(v,i));
> 0 rows inserted/updated/deleted
> ij> alter table t0 alter v set data type varchar(2);
> 0 rows inserted/updated/deleted
> ij>
> In 10.4 soft upgrade mode I cannot:
> ij> create table t0 (i int not null, v varchar(1) not null, constraint  uq unique(v,i));
> 0 rows inserted/updated/deleted
> ij> alter table t0 alter v set data type varchar(2);
> ERROR 42Z20: Column 'V' cannot be made nullable. It is part of a primary key or unique constraint, which cannot have any
> nullable columns.
> ij>

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