db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4164) Make REVOKE statement description mention what happens for open result sets/cursors
Date Fri, 17 Apr 2009 13:30:21 GMT

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

Kim Haase updated DERBY-4164:
-----------------------------

    Attachment: rrefsqljrevoke.html
                derby-4164-2.diff

Dag, this is a great explanation, but there is a bit of a run-on sentence in it. I'm attaching
a second patch (derby-4164-2.diff) that makes a few edits -- I hope it has not changed the
meaning of anything. I've also attached the output HTML page, rrefsqljrevoke.html.

> 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.diff, 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.


Mime
View raw message