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/03 19:22:12 UTC
[jira] [Updated] (DERBY-6033) Lift the arbitrary limit on the
number of routine parameters.
[ https://issues.apache.org/jira/browse/DERBY-6033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas updated DERBY-6033:
---------------------------------
Attachment: derby-6033-01-aa-liftLimit.diff
Attaching derby-6033-01-aa-liftLimit.diff. This patch removes the limit of 90 parameters per SQL routine. I am running tests now.
Touches the following files:
-----------
M java/engine/org/apache/derby/iapi/reference/Limits.java
M java/engine/org/apache/derby/impl/sql/compile/CreateAliasNode.java
Remove the limit.
-----------
M java/engine/org/apache/derby/loc/messages.xml
M java/shared/org/apache/derby/shared/common/reference/SQLState.java
Remove the corresponding error message.
-----------
M java/testing/org/apache/derbyTesting/functionTests/tests/lang/dbManagerLimits.java
M java/testing/org/apache/derbyTesting/functionTests/master/dbManagerLimits.out
Adjust the corresponding test.
> 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
> Attachments: derby-6033-01-aa-liftLimit.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