db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5111) NullPointerException on unique constraint violation with unique index
Date Thu, 20 Mar 2014 21:37:52 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942329#comment-13942329
] 

ASF subversion and git services commented on DERBY-5111:
--------------------------------------------------------

Commit 1579766 from [~dagw] in branch 'code/trunk'
[ https://svn.apache.org/r1579766 ]

DERBY-5111 NullPointerException on unique constraint violation with unique index

Patch derby-5111.

> 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
>            Assignee: Dag H. Wanvik
>              Labels: derby_triage10_11
>         Attachments: derby-5111.diff
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message