[
https://issues.apache.org/jira/browse/DERBY-6121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778915#comment-13778915
]
Dag H. Wanvik commented on DERBY-6121:
--------------------------------------
The corresponding levels are as follows: ISO vs DB2 nomenclature (cf.
http://www.ibm.com/developerworks/data/library/techarticle/dm-1107db2isolationlevel/)
Serializable RR (repeatable read)
Repeatable read RS (read stability)
Read committed CS (cursor stability)
Read uncommitted UR (uncommitted read)
Our syntax is a mix of these it seems: SERIALIZABLE obviously refers to the ISO
name (synonym RR).
REPEATABLE READ is a also a synonym for RR, and this is the DB2 meaning of
"repeatable read". SO if the user wants ISO REPETABLE READ, he needs to specify
RS, confusingly enough.
So the table is correctly aligned by this layout (according to meaning):
UR | DIRTY READ | READ UNCOMMITTED
CS | READ COMMITTED | CURSOR STABILITY
RS |
RR | REPEATABLE READ | SERIALIZABLE
as far as I can tell (see parsing logic in sqlgrammar.jj, ca line 12169. And
yes, "|" at the end of the lines.
> 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: 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
