[
https://issues.apache.org/jira/browse/DERBY-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13781853#comment-13781853
]
ASF subversion and git services commented on DERBY-6121:
--------------------------------------------------------
Commit 1527587 from [~chaase3] in branch 'docs/trunk'
[ https://svn.apache.org/r1527587 ]
DERBY-6121 Regularize how we refer to object names in the Reference Manual
Major update of Reference Manual syntax formats; added 5 topics, modified 100.
Patch: DERBY-6121.diff
> 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 was sent by Atlassian JIRA
(v6.1#6144)
