[
https://issues.apache.org/jira/browse/DERBY-6034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543686#comment-13543686
]
Knut Anders Hatlen commented on DERBY-6034:
-------------------------------------------
The patch looks fine to me. +1 to commit.
There still is a limit on how many parameters a Java method can have, but I
don't think we need to document that. Per the Java Virtual Machine
Specification, a Java method cannot have more than 255 parameters:
http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-4.html#jvms-4.11
> 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
