[
https://issues.apache.org/jira/browse/DERBY-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-6033:
--------------------------------------
Attachment: testMaxParams.diff
testMaxParams.diff adds a test case that verifies that Derby can create and
execute a procedure with the maximum number of parameters allowed by the Java
Virtual Machine specification (255, per
http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.11 ).
It also tests that stored procedures with more than 255 parameters fail
gracefully on execution. Note that DDL with > 255 parameters will not fail, as
CREATE PROCEDURE does not check whether the Java method exists. That's only
checked on execution.
Committed revision 1428775.
> Lift the arbitrary limit on the number of routine parameters.
> -------------------------------------------------------------
>
> Key: DERBY-6033
> URL: https://issues.apache.org/jira/browse/DERBY-6033
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Fix For: 10.10.0.0
>
> Attachments: derby-6033-01-aa-liftLimit.diff, testMaxParams.diff
>
>
> The number of parameters to a Derby routine is arbitrarily limited to 90.
> This limit is causing difficulties for users (see
> http://apache-database.10148.n7.nabble.com/number-of-parameters-td126108.html).
> It ought to be safe to lift this limit. Changes need to be made to
> CreateAliasNode and to the corresponding
> dbManagerLimits.testMostParametersInStoredProcedures() test.
--
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
