db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From d..@apache.org
Subject svn commit: r766179 - /db/derby/docs/branches/10.5/src/ref/rrefsqljrevoke.dita
Date Fri, 17 Apr 2009 23:26:21 GMT
Author: dag
Date: Fri Apr 17 23:26:21 2009
New Revision: 766179

URL: http://svn.apache.org/viewvc?rev=766179&view=rev
DERBY-4164 Make REVOKE statement description mention what happens for open result sets/cursors

Backported fix from trunk tp 10.5 branch as:

svn merge -c 766177 https://svn.apache.org/repos/asf/db/derby/docs/trunk.


Modified: db/derby/docs/branches/10.5/src/ref/rrefsqljrevoke.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.5/src/ref/rrefsqljrevoke.dita?rev=766179&r1=766178&r2=766179&view=diff
--- db/derby/docs/branches/10.5/src/ref/rrefsqljrevoke.dita (original)
+++ db/derby/docs/branches/10.5/src/ref/rrefsqljrevoke.dita Fri Apr 17 23:26:21 2009
@@ -115,6 +115,24 @@
 <section id="revokeroutinename"><title>routine-designator</title><codeblock><b>
    <i>qualified-name</i> [ signature ]
+  <title>Prepared statements and open result sets/cursors</title>
+  <p>
+    Checking for privileges happens at statement execution time, so
+    prepared statements are still usable after a revoke action. If
+    sufficient privileges are still available for the session,
+    prepared statements will be executed, and for queries, a result
+    set will be returned.
+  </p>
+  <p> Once a result set has been returned to the application (by
+    executing a prepared statement or by direct execution), it
+    will remain accessible even if privileges or roles are revoked in
+    a way that would cause another execution of the same statement to
+    fail.
+  </p>
 <section><title>Cascading object dependencies</title><p>For views,
 and constraints, if the privilege on which the object depends on is revoked,
 the object is automatically dropped. <ph conref="../conrefs.dita#prod/productshortname"></ph>

View raw message