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

Kim Haase commented on DERBY-6121:
----------------------------------

I understand the square brackets to enclose optional items, while the curly 
braces enclose required items that need to be separated by "|" to indicate 
choices. That's how I've always used them in syntax sections of compiler docs 
since the beginning of time (more or less). 

And I was going to say, "We document the modified BNF syntax in the Getting 
Started Guide, here": 
http://db.apache.org/derby/docs/10.10/getstart/rgsdocs10012.html

However, what it says there is incorrect, at least in terms of our customary 
usage. Looks like a separate JIRA issue.

I changed the rolename syntax to

{ GRANT roleName [ , roleName ]* TO grantees }

I should enclose the privilege-list syntax in curly braces.

I already changed "column list" to "column-list". 
                
> 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

Reply via email to