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-6346) NPE in left join whose inner table has a generated column
Date Wed, 18 Sep 2013 12:12:59 GMT

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

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

Commit 1524385 from [~rhillegas] in branch 'code/branches/10.10'
[ https://svn.apache.org/r1524385 ]

DERBY-6346: Port 1524194 from trunk to 10.10 branch.
                
> NPE in left join whose inner table has a generated column
> ---------------------------------------------------------
>
>                 Key: DERBY-6346
>                 URL: https://issues.apache.org/jira/browse/DERBY-6346
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.5.1.1
>            Reporter: Rick Hillegas
>         Attachments: derby-6346-01-aa-logJavaException.diff, derby-6346-02-aa-generateNullForLeftJoins.diff
>
>
> Derby trips over an NPE while processing a left join whose inner table has a generated
column. The NPE is not printed to derby.log, indicating another problem. The bug goes as far
back as 10.5.1.1, the release which introduced generated columns. The NPE does NOT crash the
connection. The application can continue issuing statements on the connection.
> The following script shows this problem:
> connect 'jdbc:derby:memory:db;create=true';
> create table t1( c1 int, c2 int generated always as ( -c1 ) );
> create table t2( c1 int );
> insert into t1( c1 ) values ( 2 ), ( 20 );
> insert into t2( c1 ) values ( 2 ), ( 200 );
> -- raises a SQLException wrapping an NPE
> select * from t2 left join t1 on t1.c1 = t2.c1;

--
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

Mime
View raw message