svn commit: r766177 - /db/derby/docs/trunk/src/ref/rrefsqljrevoke.dita

[da...@apache.org]

Author: dag
Date: Fri Apr 17 23:13:24 2009
New Revision: 766177

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

Patch derby-4164-4 which adds such a description.

Modified:
    db/derby/docs/trunk/src/ref/rrefsqljrevoke.dita

Modified: db/derby/docs/trunk/src/ref/rrefsqljrevoke.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefsqljrevoke.dita?rev=766177&r1=766176&r2=766177&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefsqljrevoke.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefsqljrevoke.dita Fri Apr 17 23:13:24 2009
@@ -115,6 +115,24 @@
 <section id="revokeroutinename"><title>routine-designator</title><codeblock><b>  {
    <i>qualified-name</i> [ signature ]
   }</b></codeblock></section>
+
+<section>
+  <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>
+
 <section><title>Cascading object dependencies</title><p>For views, triggers,
 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> does