[
https://issues.apache.org/jira/browse/DERBY-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-1963:
----------------------------------
the issue being reported is a problem with the parameter name "paramOne" - not
the function name. The problem will show up if you use a jdbc interface that
requires the parameter name rather than a ordernal of the parameter. Also I
assume the metadata will be wrong.
> Routine parameter names displayed by dblook are not escaped.
> ------------------------------------------------------------
>
> Key: DERBY-1963
> URL: https://issues.apache.org/jira/browse/DERBY-1963
> Project: Derby
> Issue Type: Bug
> Components: Tools
> Affects Versions: 10.3.0.0
> Reporter: Daniel John Debrunner
> Priority: Minor
> Fix For: 10.3.0.0
>
>
> After using this SQL to create a function with a delimited parameter name
> CREATE FUNCTION FRED ("paramOne" INTEGER) RETURNS INTEGER
> LANGUAGE JAVA PARAMETER STYLE JAVA
> EXTERNAL NAME 'fred.foo'
> dblook will output a CREATE FUNCTION statement with the parameter name
> without quotes:
> CREATE FUNCTION "APP"."FRED" (paramOne INTEGER) RETURNS INTEGER
> LANGUAGE JAVA PARAMETER STYLE JAVA
> READS SQL DATA CALLED ON NULL INPUT
> EXTERNAL NAME 'fred.foo';
> Using the output from dblook to re-create the function will result in a
> function with a different parameter name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
