Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.2814 05/06/17 09:56:34 paul@stripped +3 -0
A few remarks about DETERMINISTIC.
refman/stored-procedures.xml
1.2 05/06/17 09:56:32 paul@stripped +28 -5
A few remarks about DETERMINISTIC.
refman-5.0/stored-procedures.xml
1.2 05/06/17 09:56:32 paul@stripped +28 -5
Sync.
refman-4.1/stored-procedures.xml
1.2 05/06/17 09:56:32 paul@stripped +28 -5
Sync.
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: paul
# Host: frost.snake.net
# Root: /Volumes/frost2/MySQL/bk/mysqldoc
--- 1.1/refman-4.1/stored-procedures.xml 2005-06-16 14:35:23 -05:00
+++ 1.2/refman-4.1/stored-procedures.xml 2005-06-17 09:56:32 -05:00
@@ -299,12 +299,35 @@
</para>
<para>
- A procedure or function is considered ``deterministic'' if it always
- produces the same result for the same input parameters, and ``not
- deterministic'' otherwise. Currently, the
- <literal>DETERMINISTIC</literal> characteristic is accepted, but not
- yet used by the optimizer.
+ A procedure or function is considered <quote>deterministic</quote>
+ if it always produces the same result for the same input parameters,
+ and <quote>not deterministic</quote> otherwise. If neither
+ <literal>DETERMINISTIC</literal> nor <literal>NOT
+ DETERMINISTIC</literal> is given, the default is <literal>NOT
+ DETERMINISTIC</literal>.
</para>
+
+ <para>
+ For replication purposes, use of the <literal>NOW()</literal>
+ function (or its synonyms) or <literal>RAND()</literal> does not
+ necessarily make a routine non-deterministic. For
+ <literal>NOW()</literal>, the binary log includes the timestamp and
+ replicates correctly. <literal>RAND()</literal> also replicates
+ correctly as long as it is invoked only once within a routine. (You
+ can consider the routine execution timestamp and random number see
+ as implicit inputs that are identical on the master and slave.)
+ </para>
+
+ <para>
+ Currently, the <literal>DETERMINISTIC</literal> characteristic is
+ accepted, but not yet used by the optimizer.
+ </para>
+
+<!--
+TODO:
+But [NOT] DETERMINISTIC does have implications for routine creations,
+as still needs to be described.
+-->
<para>
The <literal>SQL SECURITY</literal> characteristic can be used to
--- 1.1/refman-5.0/stored-procedures.xml 2005-06-16 14:46:22 -05:00
+++ 1.2/refman-5.0/stored-procedures.xml 2005-06-17 09:56:32 -05:00
@@ -299,12 +299,35 @@
</para>
<para>
- A procedure or function is considered ``deterministic'' if it always
- produces the same result for the same input parameters, and ``not
- deterministic'' otherwise. Currently, the
- <literal>DETERMINISTIC</literal> characteristic is accepted, but not
- yet used by the optimizer.
+ A procedure or function is considered <quote>deterministic</quote>
+ if it always produces the same result for the same input parameters,
+ and <quote>not deterministic</quote> otherwise. If neither
+ <literal>DETERMINISTIC</literal> nor <literal>NOT
+ DETERMINISTIC</literal> is given, the default is <literal>NOT
+ DETERMINISTIC</literal>.
</para>
+
+ <para>
+ For replication purposes, use of the <literal>NOW()</literal>
+ function (or its synonyms) or <literal>RAND()</literal> does not
+ necessarily make a routine non-deterministic. For
+ <literal>NOW()</literal>, the binary log includes the timestamp and
+ replicates correctly. <literal>RAND()</literal> also replicates
+ correctly as long as it is invoked only once within a routine. (You
+ can consider the routine execution timestamp and random number see
+ as implicit inputs that are identical on the master and slave.)
+ </para>
+
+ <para>
+ Currently, the <literal>DETERMINISTIC</literal> characteristic is
+ accepted, but not yet used by the optimizer.
+ </para>
+
+<!--
+TODO:
+But [NOT] DETERMINISTIC does have implications for routine creations,
+as still needs to be described.
+-->
<para>
The <literal>SQL SECURITY</literal> characteristic can be used to
--- 1.1/refman/stored-procedures.xml 2005-06-15 18:46:58 -05:00
+++ 1.2/refman/stored-procedures.xml 2005-06-17 09:56:32 -05:00
@@ -299,12 +299,35 @@
</para>
<para>
- A procedure or function is considered ``deterministic'' if it always
- produces the same result for the same input parameters, and ``not
- deterministic'' otherwise. Currently, the
- <literal>DETERMINISTIC</literal> characteristic is accepted, but not
- yet used by the optimizer.
+ A procedure or function is considered <quote>deterministic</quote>
+ if it always produces the same result for the same input parameters,
+ and <quote>not deterministic</quote> otherwise. If neither
+ <literal>DETERMINISTIC</literal> nor <literal>NOT
+ DETERMINISTIC</literal> is given, the default is <literal>NOT
+ DETERMINISTIC</literal>.
</para>
+
+ <para>
+ For replication purposes, use of the <literal>NOW()</literal>
+ function (or its synonyms) or <literal>RAND()</literal> does not
+ necessarily make a routine non-deterministic. For
+ <literal>NOW()</literal>, the binary log includes the timestamp and
+ replicates correctly. <literal>RAND()</literal> also replicates
+ correctly as long as it is invoked only once within a routine. (You
+ can consider the routine execution timestamp and random number see
+ as implicit inputs that are identical on the master and slave.)
+ </para>
+
+ <para>
+ Currently, the <literal>DETERMINISTIC</literal> characteristic is
+ accepted, but not yet used by the optimizer.
+ </para>
+
+<!--
+TODO:
+But [NOT] DETERMINISTIC does have implications for routine creations,
+as still needs to be described.
+-->
<para>
The <literal>SQL SECURITY</literal> characteristic can be used to
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.2814) | paul | 17 Jun |
