[
https://issues.apache.org/jira/browse/DERBY-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777536#comment-13777536
]
Kim Haase commented on DERBY-6121:
----------------------------------
Does anyone have any thoughts one way or the other about whether syntax should
use hyphenated lower camel case (table-Name, role-Name) or non-hyphenated lower
camel case (tableName, roleName)? Some syntax uses upper camel case
(SelectExpression, TableExpression, ScalarSubquery). That's another possibility.
More of the existing topics are hyphenated than not, but I'm not crazy about
the look. This is turning into a rather large syntax overhaul, and we may as
well do it right.
Any preferences?
> Regularize how we refer to object names in the Reference Manual sections on
> GRANT/REVOKE
> ----------------------------------------------------------------------------------------
>
> 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
>
> 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
