[
https://issues.apache.org/jira/browse/DERBY-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700374#action_12700374
]
Dag H. Wanvik commented on DERBY-4164:
--------------------------------------
Backported to 10.5 docs branch as:
svn merge -c 766177 https://svn.apache.org/repos/asf/db/derby/docs/trunk
Committed as svn 766179, closing.
> Make REVOKE statement description mention what happens for open result
> sets/cursors
> -----------------------------------------------------------------------------------
>
> Key: DERBY-4164
> URL: https://issues.apache.org/jira/browse/DERBY-4164
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Dag H. Wanvik
> Priority: Minor
> Fix For: 10.5.1.2, 10.6.0.0
>
> Attachments: derby-4164-2.diff, derby-4164-3.diff, derby-4164-4.diff,
> derby-4164.diff, rrefsqljrevoke-3.html, rrefsqljrevoke-4.html,
> rrefsqljrevoke.html
>
>
> When a REVOKE statement is executed, already open result sets are not
> impacted. This should be mentioned
> in the user documentation, at least here: ref/rrefsqljrevoke.html.
> Permissions are checked at statement execute time; if this succeeds, a
> cursor/result set will be able to access all rows
> in the result set even if privileges/roles are revoked after the execute but
> before the result set/cursor is closed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
