You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2013/01/18 16:34:17 UTC

[jira] [Assigned] (DERBY-6047) NPE in StaticCallMethod#coerceMethodParameter with a constant argument to INOUT parameter

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

Rick Hillegas reassigned DERBY-6047:
------------------------------------

    Assignee: Rick Hillegas
    
> NPE in StaticCallMethod#coerceMethodParameter with a constant argument to INOUT parameter
> -----------------------------------------------------------------------------------------
>
>                 Key: DERBY-6047
>                 URL: https://issues.apache.org/jira/browse/DERBY-6047
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>            Reporter: Dag H. Wanvik
>            Assignee: Rick Hillegas
>
> The following repro shows the problem (provided by Holger Rehn, cf. issue DERBY-5945).
>         sta.execute( "create procedure PROC( inout x int ) " + 
>             "parameter style java modifies sql data language java " + 
>             "external name 'DUMMY.PROC'" );
>         sta.execute( "{call PROC(1)}" );
> gives NPE on trunk (even before the fixes introduced for DERBY-5945), but not on 10.9, so I believe it's a regression:
> :
> Caused by: java.lang.NullPointerException
> ...sql.compile.StaticMethodCallNode.coerceMethodParameter(StaticMethodCallNode.java:702)
> ...sql.compile.StaticMethodCallNode.resolveRoutine(StaticMethodCallNode.java:620)
> ...sql.compile.StaticMethodCallNode.bindExpression(StaticMethodCallNode.java:210)
> ...sql.compile.JavaToSQLValueNode.bindExpression(JavaToSQLValueNode.java:237)
> ...sql.compile.CallStatementNode.bindStatement(CallStatementNode.java:126)
> ...sql.GenericStatement.prepMinion(GenericStatement.java:400)
> :

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