Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1B79AF06B for ; Fri, 19 Apr 2013 16:05:18 +0000 (UTC) Received: (qmail 39657 invoked by uid 500); 19 Apr 2013 16:05:17 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 39448 invoked by uid 500); 19 Apr 2013 16:05:17 -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 39406 invoked by uid 99); 19 Apr 2013 16:05:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Apr 2013 16:05:16 +0000 Date: Fri, 19 Apr 2013 16:05:16 +0000 (UTC) From: "Mike Matrigali (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-5111) NullPointerException on unique constraint violation with unique index MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Matrigali updated DERBY-5111: ---------------------------------- Issue & fix info: High Value Fix,Repro attached (was: Repro attached) Affects Version/s: 10.11.0.0 Bug behavior facts: Crash,Seen in production > NullPointerException on unique constraint violation with unique index > --------------------------------------------------------------------- > > Key: DERBY-5111 > URL: https://issues.apache.org/jira/browse/DERBY-5111 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.6.1.0, 10.6.2.1, 10.7.1.1, 10.11.0.0 > Reporter: Mark La Rue > Labels: derby_triage10_9 > > Given the below DDL, violations of the unique constraint (an example follows the DDL) specified on table t1 will result in a NullPointerException that terminates the active connection. The root cause appears to be related to the unique indexes; removing them results in the correct constraint violation. > CREATE TABLE s.t0 (t0_id INTEGER NOT NULL, value VARCHAR(75) NOT NULL); > ALTER TABLE s.t0 ADD CONSTRAINT pk_1 PRIMARY KEY (t0_id); > CREATE TABLE s.t1 (t1_id INTEGER NOT NULL, t0_id INTEGER NOT NULL, value VARCHAR(75) NOT NULL); > CREATE UNIQUE INDEX s.ui_1 ON s.t1 (t1_id); > ALTER TABLE s.t1 ADD CONSTRAINT pk_2 PRIMARY KEY (t1_id); > ALTER TABLE s.t1 ADD CONSTRAINT fk_1 FOREIGN KEY (t0_id) REFERENCES s.t0 (t0_id) ON DELETE CASCADE; > CREATE UNIQUE INDEX s.ui_2 ON s.t1 (t0_id, value); > ALTER TABLE s.t1 ADD CONSTRAINT uc_1 UNIQUE (t0_id, value); > Minimal DML to trigger the constraint violation: > INSERT INTO s.t0 VALUES (0, 'foobar'); > INSERT INTO s.t1 VALUES(0, 0, 'Test'); > INSERT INTO s.t1 VALUES(1, 0, 'Test'); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira