db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bpendle...@apache.org
Subject svn commit: r833268 - /db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita
Date Fri, 06 Nov 2009 01:00:00 GMT
Author: bpendleton
Date: Fri Nov  6 00:59:59 2009
New Revision: 833268

URL: http://svn.apache.org/viewvc?rev=833268&view=rev
Log:
DERBY-3062: Clarify the documentation for the CREATE PROCEDURE command

This change clarifies the reference manual page for the CREATE PROCEDURE
command to make the description of the

  NO SQL | MODIFIES SQL DATA | CONTAINS SQL | READS SQL DATA

clause simpler and easier to read.

Discussion on the derby-dev list led to the conclusion that there are
currently no SQL statements which are flatly prohibited in a Java stored
procedure, so the text about such statements was removed, and the remaining
text was adjusted to be simpler.

Note that the other issue in DERBY-3062, regarding the documentation of the
SYSCS_EXPORT_TABLE system procedure, was addressed during the documentation
of the 10.4 release.

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

Modified: db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita?rev=833268&r1=833267&r2=833268&view=diff
==============================================================================
--- db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita (original)
+++ db/derby/docs/trunk/src/ref/rrefcreateprocedurestatement.dita Fri Nov  6 00:59:59 2009
@@ -94,25 +94,27 @@
 not support long column types (for example Long Varchar, BLOB, and so on).
 An error will occur if you try to use one of these long column types. </p></section>
 <section><title>NO SQL, CONTAINS SQL, READS SQL DATA, MODIFIES SQL DATA </title>
<p>Indicates
-whether the stored procedure issues any SQL statements and, if so, what type.</p> <dl>
+        whether the stored procedure issues any SQL statements and, if so, what type.
+    MODIFIES SQL DATA is the default value.
+    A stored procedure which issues a statement which does not conform to
+    the declared SQL statement level will cause Derby to throw an exception.
+        </p> <dl>
 <dlentry>
-<dt>CONTAINS SQL</dt>
-<dd>Indicates that SQL statements that neither read nor modify SQL data can
-be executed by the stored procedure. Statements that are not supported in
-any stored procedure return a different error. MODIFIES SQL DATA is the default
-value.</dd>
-</dlentry><dlentry>
 <dt>NO SQL</dt>
 <dd>Indicates that the stored procedure cannot execute any SQL statements</dd>
 </dlentry><dlentry>
+<dt>CONTAINS SQL</dt>
+<dd>Indicates that SQL statements that neither read nor modify SQL data can
+    be executed by the stored procedure.
+</dd>
+</dlentry><dlentry>
 <dt>READS SQL DATA </dt>
-<dd>Indicates that some SQL statements that do not modify SQL data can be
-included in the stored procedure. Statements that are not supported in any
-stored procedure return a different error.</dd>
+<dd>Indicates that SQL statements that do not modify SQL data (for
+    example, SELECT statements) can be included in the stored procedure.
+</dd>
 </dlentry><dlentry>
 <dt>MODIFIES SQL DATA</dt>
-<dd>Indicates that the stored procedure can execute any SQL statement except
-statements that are not supported in stored procedures.</dd>
+<dd>Indicates that the stored procedure can execute any SQL statement.</dd>
 </dlentry></dl></section>
 <section><p>The procedure elements may appear in any order, but each type
 of element can only appear once. A procedure definition must contain these



Mime
View raw message