[
https://issues.apache.org/jira/browse/DERBY-3069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3069:
---------------------------------
Attachment: derby-3069-04-aa-shortenRoutineNamesInUpgradeTest.diff
Attaching derby-3069-04-aa-shortenRoutineNamesInUpgradeTest.diff. My previous
submission raised an error in the upgrade tests. This patch should fix that
problem. Committed at subversion revision 1418022.
The problem was that my new upgrade test created functions and procedures with
names which were longer than 18 characters. In 10.0, the very first release of
Derby, that's the limit on the length of SQL identifiers. In 10.1, the limit
was raised to 128 (see submission 170069 by Sateesh).
This patch shortens the lengths of the problematic identifiers. With this
patch, the upgrade tests run cleanly for me when the initial release is
10.0.2.1.
Touches the following file:
M
java/testing/org/apache/derbyTesting/functionTests/tests/upgradeTests/Changes10_10.java
> Derby does not resolve functions bound to methods with varargs.
> ---------------------------------------------------------------
>
> Key: DERBY-3069
> URL: https://issues.apache.org/jira/browse/DERBY-3069
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.0.2.0, 10.0.2.1, 10.1.1.0, 10.1.2.1, 10.1.3.1,
> 10.2.1.6, 10.2.2.0, 10.3.1.4
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Labels: derby_triage10_10
> Attachments: derby-3069-01-varargs-aa.diff,
> derby-3069-01-varargs-ab.diff, derby-3069-02-backout.diff,
> derby-3069-03-aa-varargsSyntax.diff, derby-3069-03-ab-varargsSyntax.diff,
> derby-3069-04-aa-shortenRoutineNamesInUpgradeTest.diff, Varargs.html, z.java,
> z.sql
>
>
> Varargs were added in Java 5. It would be nice if Derby let you invoke a
> function bound to a method with a variable length argument list. The
> Reference Guide states a small number of restrictions for methods which can
> be invoked as Derby functions: They must be public, static, and not have
> arguments which are long datatypes. I see no reason that Derby shouldn't be
> able to resolve and invoke functions which are bound to methods which don't
> suffer these limitations but which have variable argument lists.
--
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
