db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5954) NPE in SELECT involving subselects and windows functions
Date Mon, 29 Oct 2012 17:34:13 GMT

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

Kathey Marsden commented on DERBY-5954:

I would really like this fix in 10.8.3 and think it would be worthwhile to hold up the release
up to another week as this is a regression and a fix needed by a user in 10.8 but Bryan's
comments seem serious:

"Just thinking abstractly, it seems like there are two different ways that the new
visitor code could be wrong:
1) It could fail to descend into a sub-query when in fact it should, or
2) It could descend into a sub-query that it shouldn't descend into."

Bryan, do you think the patch might potentially cause a  different regression?  Dag, what
are your thoughts on this?



> NPE in SELECT involving subselects and windows functions
> --------------------------------------------------------
>                 Key: DERBY-5954
>                 URL: https://issues.apache.org/jira/browse/DERBY-5954
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions:,,,,,
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>         Attachments: derby-5954.diff, derby-5954-with-test.diff, derby-5954-with-test.stat
> A user reports and I have verified an NPE on the following SELECT:
> connect 'jdbc:derby:memory:db;create=true';
> create table blah ( a int );
> insert into blah values (1), (2), (3), (4), (5), (6), (7);
> SELECT rn, (SELECT rn FROM (SELECT row_number() over() rn FROM blah ) as T2
> where T2.rn = T1.rn+1) rn2
> FROM (SELECT row_number() over() rn from blah) as T1;

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

View raw message