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

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

    Attachment: DERBY-6121.zip
                DERBY-6121.stat
                DERBY-6121.diff

Attaching DERBY-6121.diff, DERBY-6121.stat, and DERBY-6121.zip, with 5 new 
topics and changes to 100 other files including the map file. 

I decided to fix the SET ISOLATION syntax while I was at it, rather than forget 
to file a new issue for it.

There are still plenty of syntax inconsistencies, which may become more obvious 
once these fixes are in. 

Please let me know if this seems like the right direction to go in. If it is, 
it might make sense to commit this patch and then make additional fixes in 
smaller patches. For instance, I plan to make another patch to camelcase the 
arguments in the function topics. 

                
> 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
>         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

Reply via email to