Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 56913 invoked from network); 6 Jul 2009 20:45:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Jul 2009 20:45:27 -0000 Received: (qmail 13960 invoked by uid 500); 6 Jul 2009 20:45:37 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 13907 invoked by uid 500); 6 Jul 2009 20:45:37 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 13895 invoked by uid 99); 6 Jul 2009 20:45:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jul 2009 20:45:37 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jul 2009 20:45:35 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DBB82234C004 for ; Mon, 6 Jul 2009 13:45:14 -0700 (PDT) Message-ID: <554124358.1246913114884.JavaMail.jira@brutus> Date: Mon, 6 Jul 2009 13:45:14 -0700 (PDT) From: "Tiago R. Espinha (JIRA)" To: derby-dev@db.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 In-Reply-To: <976084676.1205254246221.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tiago R. Espinha updated DERBY-3523: ------------------------------------ Urgency: Low Triaged for 10.5.2. It seems like this issue is fixed. Kathey, can you resolve if it is? > 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 > Components: SQL > Affects Versions: 10.4.1.3, 10.5.1.1 > 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.