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

Rick Hillegas commented on DERBY-6121:
--------------------------------------

Hi Kim,

Looks nice. +1 to this increment. A couple comments follow:

o I wonder if "JOIN operations" should be "joinOperation" in rrefjdbc37244.

Some responses to your questions:

> 2) The topic on the CHAR function (rrefbuiltchar.html) mentions using
>  the "DECIMAL scalar function". I can't find any reference to this
>  function. Do you have any idea what is being referred to here?
>  There's a long list of scalar functions in "JDBC escape syntax for fn
>  keyword" (rrefjdbc88908.html), but "decimal" is not among them.

I can't find any reference to a DECIMAL scalar function in the current 
Reference Manual or in the Reference Manuals for Cloudscape 3.5 or 5.1. 
However, I see that DB2 supports such a function: 
https://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=%2Fcom.ibm.db2.udb.admin.doc%2Fdoc%2Fr0000791.htm
 Maybe this is left over from a Cloudscape version produced after 5.1 but 
before Derby was open-sourced. I would recommend striking this confusing 
sentence.

> 3) I notice that for all the functions that take a DOUBLE argument,
> there is a link to the topic on that data type. Topics that take other
> kinds of arguments often don't link to the topics on those data types
> (see the DATE function topic, rrefdatefunc.html, or the LTRIM function
> topic, rrefsqlj97870.html, for example). Would it be useful to add
> these links? Or should we not bother?

It is puzzling that this is only done regularly for DOUBLE PRECISION. Note that 
rreffuncrand hot-links to both DOUBLE PRECISION and INTEGER. My question would 
be: where do we draw the line? Do we want to go through the whole Reference 
Manual and regularize this? I can see that these hotlinks are convenient but 
I'm not sure this is worth doing if it's a big rototill.

Thanks,
-Rick


> Regularize how we refer to object names in the Reference Manual
> ---------------------------------------------------------------
>
>                 Key: DERBY-6121
>                 URL: https://issues.apache.org/jira/browse/DERBY-6121
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.10.1.1
>            Reporter: Rick Hillegas
>            Assignee: Kim Haase
>         Attachments: DERBY-6121-2.diff, DERBY-6121-2.stat, DERBY-6121-2.zip, 
> DERBY-6121.diff, DERBY-6121.stat, DERBY-6121.zip, rrefsqlj32268.html
>
>
> This issue came up during the buddy testing of user-defined aggregates. 
> Here's what Dag discovered:
>     identifiers (seen when looking at GRANT USAGE of aggregates): 
> "table-Name" occurences are linked to a section explainig them 
> (rreftablename.html), but UDA names are defined in-lined as 
>       GRANT USAGE ON DERBY AGGREGATE [ schemaName. ] SQL92Identifier TO 
> grantees
>     In a third variant, 
>       GRANT EXECUTE ON { FUNCTION | PROCEDURE } routine-designator TO grantees
>     routine-designator is defined locally as 
>       routine-designator { function-name | procedure-name }  
>     without links to what "function-name" or "procedure-name" might look 
> like. It would be good to harmonize the latter two forms to a central 
> definition as for "table-Name".
>     Finally, I noted that the definition page for SchemaName doesn't link to 
> the SQL92Identifier page... 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to