[
https://issues.apache.org/jira/browse/DERBY-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700268#action_12700268
]
Kim Haase commented on DERBY-4164:
----------------------------------
I don't think you need a separate section, since the title covers open result
sets in general -- but it might be helpful to change the sentence to say
something like
Once a result set has been returned to the application (by a prepared
statement or by direct execution), ...
Though I'm not exactly sure what "direct execution" covers -- execution of an
ordinary Statement rather than a prepared one?
> 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
> Priority: Minor
> Fix For: 10.6.0.0
>
> Attachments: derby-4164-2.diff, derby-4164-3.diff, derby-4164.diff,
> rrefsqljrevoke-3.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.
