db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4410) NullPointerException when USING clause contains all columns in both join tables
Date Mon, 19 Oct 2009 15:41:59 GMT

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

Knut Anders Hatlen updated DERBY-4410:
--------------------------------------

    Attachment: adjustIndex.diff

The attached patch appears to fix the problem. It changes the loop so that the index is adjusted
after elements have been removed from or added to the RCL. This should fix both the harmless
double processing and the problematic skipping of elements.

The patch does not include a regression test, and none of the existsing regression tests have
been run yet.

> NullPointerException when USING clause contains all columns in both join tables
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-4410
>                 URL: https://issues.apache.org/jira/browse/DERBY-4410
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.6.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>         Attachments: adjustIndex.diff
>
>
> ij> create table t(x int);
> 0 rows inserted/updated/deleted
> ij> select t1.*, t2.* from t t1 join t t2 using (x);
> ERROR XJ001: Java exception: ': java.lang.NullPointerException'.
> This statement should have raised an exception because both t1.* and t2.* expand to no
columns. See DERBY-4407.

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


Mime
View raw message