[
https://issues.apache.org/jira/browse/DERBY-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase resolved DERBY-6034.
------------------------------
Resolution: Fixed
Issue & fix info: (was: Patch Available)
Thanks, Knut!
Committed patch DERBY-6034.diff to documentation trunk at revision 1428902.
I agree that we don't have to duplicate documentation about JVM limits. It is
interesting that according to that section in the SE spec, the limit could be
less than 255 if some parameters are large in size: "Note that a method
descriptor is defined in terms of a notion of method parameter length in which
a parameter of type long or double contributes two units to the length, so
parameters of these types further reduce the limit." I hope our tests account
for that.
> Fix documentation on procedure argument limits
> ----------------------------------------------
>
> Key: DERBY-6034
> URL: https://issues.apache.org/jira/browse/DERBY-6034
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 10.10.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Fix For: 10.10.0.0
>
> Attachments: DERBY-6034.diff, rrefdbmlimits.html
>
>
> The table in the Reference Manual topic "Limitations for database values"
> currently states that the maximum number of parameters in a stored procedure
> is 90. Should this table row simply be removed? I gather there is no limit
> any more.
> If I find other references to the limit, I'll fix them too.
--
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
