[jira] [Updated] (DERBY-6121) Regularize how we refer to object names in the Reference Manual

["Kim Haase (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase updated DERBY-6121:
-----------------------------

    Issue & fix info: Patch Available
    
> 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.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 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