db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-258) Incorrect method resolution with explicit method signature
Date Fri, 03 Jun 2005 19:04:58 GMT
    [ http://issues.apache.org/jira/browse/DERBY-258?page=comments#action_12312553 ] 

Daniel John Debrunner commented on DERBY-258:
---------------------------------------------

Other example that lead to incorrect resolution (all cause issues when called)

-- function with more types in signature than parameters, tries to resolve to
-- int toString(int, int) [note return type should be String]
CREATE FUNCTION SIGNATURE_BUG_DERBY_258_B(A INT) RETURNS VARCHAR(128) 
LANGUAGE JAVA PARAMETER STYLE JAVA
EXTERNAL NAME 'java.lang.Integer.toString(int, int)

-- procedure with less types in signature than arguments, causes an array out of bounds exception
CREATE PROCEDURE SIGNATURE_BUG_DERBY_258_C(IN A INT)
LANGUAGE JAVA PARAMETER STYLE JAVA 
EXTERNAL NAME 'java.lang.System.gc()'

-- any method signature that  leads to a method that does not exist
-- causes a null pointer exception
CREATE FUNCTION SIGNATURE_BUG_DERBY_258_E(P_VAL INT, P_RADIX INT) RETURNS VARCHAR(20)
LANGUAGE JAVA PARAMETER STYLE JAVA EXTERNAL NAME 'java.lang.Integer.toXXString()';

-- this valid first function defintion fails to resolve where as rhe second (with no signature)
succeeds
CREATE FUNCTION SIGNATURE_BUG_DERBY_258_D(P_VAL INT, P_RADIX INT) RETURNS VARCHAR(20)
LANGUAGE JAVA PARAMETER STYLE JAVA EXTERNAL NAME 'java.lang.Integer.toString(int, int)';
CREATE FUNCTION SIGNATURE_BUG_DERBY_258_NS(P_VAL INT, P_RADIX INT) RETURNS VARCHAR(20)
LANGUAGE JAVA PARAMETER STYLE JAVA EXTERNAL NAME 'java.lang.Integer.toString';

> Incorrect method resolution with explicit method signature
> ----------------------------------------------------------
>
>          Key: DERBY-258
>          URL: http://issues.apache.org/jira/browse/DERBY-258
>      Project: Derby
>         Type: Bug
>   Components: SQL
>     Versions: 10.1.0.0
>     Reporter: Daniel John Debrunner
>     Assignee: Daniel John Debrunner

>
> If an explicit method signature has Java type that does not match the correct SQL to
Java mapping as defined by JDBC, then method resolution seems to try and pick the incorrect
method.
> With this example an attempt is made to force an INT procedure parameter to resolve to
a java.lang.String, which is not supported. However the engine trys to resolve to a method
with an Integr parameter.
> ij> CREATE PROCEDURE SIGNATURE_BUG_1(IN A INT)
>   LANGUAGE JAVA PARAMETER STYLE JAVA
>   EXTERNAL NAME 'java.lang.System.load(java.lang.String)';
> 0 rows inserted/updated/deleted
> ij> CALL SIGNATURE_BUG_1(4);
> ERROR 38000: The exception 'java.lang.NoSuchMethodError: java.lang.System.load(Ljava/lang/Integer;)V'
was thrown while evaluating an expression.
> ERROR XJ001: Java exception: 'java.lang.System.load(Ljava/lang/Integer;)V: java.lang.NoSuchMethodError'.
> I believe that the resolution should fail with an illegal conversion error if the supplied
Java type is not a match for the SQL type according to JDBC, in this case int or java.lang.Integer.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message