[
https://issues.apache.org/jira/browse/DERBY-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-6120:
-----------------------------
Attachment: DERBY-6120.zip
DERBY-6120.stat
DERBY-6120.diff
Attaching DERBY-6120.diff, DERBY-6120.stat, and DERBY-6120.zip, with the
following changes:
A src/ref/rrefsqljexternalname.dita
M src/ref/refderby.ditamap
M src/ref/rrefcreatefunctionstatement.dita
M src/ref/rrefcreateprocedurestatement.dita
M src/ref/rrefsqljcreatetype.dita
M src/ref/rrefsqljcreateaggregate.dita
There seemed to be some inconsistencies in the sections on procedureElement and
functionElement concerning what was linked to or treated as a variable and what
wasn't, so I am afraid I made a bunch of fixes a little far afield from this
issue. I hope they are all right.
> Clarify that $ is the separator character which should be used for the
> external names of static nested classes
> --------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6120
> URL: https://issues.apache.org/jira/browse/DERBY-6120
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
> Assignee: Kim Haase
> Attachments: DERBY-6120.diff, DERBY-6120.stat, DERBY-6120.zip
>
>
> Various user-defined objects can be created which are bound to Java methods
> or classes via "external name" clauses. It's easy to mis-phrase the Java
> class name in the "external name" clause if the class is a static nested
> class. The affected objects include:
> o Functions
> o Procedures
> o Types
> o Aggregates
> Consider the following class:
> public class TestFuncs
> {
> public static final class Foo
> {
> public static double pow( double base, double power ) { return
> Math.pow( base, power ); }
> }
> }
> If the pow method is bound to a user-defined function via a CREATE FUNCTION
> command, its external name should be TestFuncs$Foo.pow, NOT TestFuncs.Foo.pow.
> We should add a section to the Reference Manual clarifying how to phrase the
> external name if it includes a reference to a static nested class. The
> detailed sections for the various user-defined objects can then refer to this
> new section.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
