db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6120) Clarify that $ is the separator character which should be used for the external names of static nested classes
Date Thu, 10 Oct 2013 15:49:43 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791602#comment-13791602
] 

Kim Haase commented on DERBY-6120:
----------------------------------

Committed patch DERBY-6120.diff to documentation trunk at revision 1531025. 
Merged to 10.10 doc branch at revision 1531031.


> 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)

Mime
View raw message