[
https://issues.apache.org/jira/browse/DERBY-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647451#comment-13647451
]
Knut Anders Hatlen commented on DERBY-6212:
-------------------------------------------
The query fails because CallStatementNode passes a null SubqueryList into
bindExpression(), which subsequently fails when trying to add a SubqueryNode to
the null list. One simple fix might be to make CallStatementNode pass a
non-null SubqueryList argument and check that it's empty after the statement
has been bound. It still won't be possible to use sub-queries as arguments to
CALL statements, but at least they would fail with a syntax error rather than a
NullPointerException.
> NullPointerException when calling a procedure with sub-query as argument
> ------------------------------------------------------------------------
>
> Key: DERBY-6212
> URL: https://issues.apache.org/jira/browse/DERBY-6212
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.10.1.1
> Reporter: Knut Anders Hatlen
> Priority: Minor
>
> ij version 10.10
> ij> connect 'jdbc:derby:memory:db;create=true';
> ij> call syscs_util.syscs_set_database_property('abc', (values 'def'));
> ERROR XJ001: Java exception: ': java.lang.NullPointerException'. (errorCode =
> 0)
> The query should either compile and execute just fine, or it should raise a
> proper exception. It should not fail with a NullPointerException.
--
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
