svn commit - mysqldoc@docsrva: r4458 - in trunk: refman-5.0 refman-5.1

[paul]

Author: paul
Date: 2007-01-11 21:38:59 +0100 (Thu, 11 Jan 2007)
New Revision: 4458

Log:
Triggers and events (just like stored routines), execute with the
sql_mode setting in force at the time of object creation. (Bug#24610)


Modified:
   trunk/refman-5.0/stored-procedures.xml
   trunk/refman-5.0/triggers.xml
   trunk/refman-5.1/events.xml
   trunk/refman-5.1/stored-procedures.xml
   trunk/refman-5.1/triggers.xml


Modified: trunk/refman-5.0/stored-procedures.xml
===================================================================
--- trunk/refman-5.0/stored-procedures.xml	2007-01-11 18:34:26 UTC (rev 4457)
+++ trunk/refman-5.0/stored-procedures.xml	2007-01-11 20:38:59 UTC (rev 4458)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 6; 1205 bytes

@@ -431,6 +431,13 @@
         <xref linkend="routine-restrictions"/>.
       </para>
 
+      <para>
+        MySQL stores the <literal>sql_mode</literal> system variable
+        setting that is in effect at the time a routine is created, and
+        always executes the routine with this setting in force,
+        <emphasis>regardless of the current server SQL mode</emphasis>.
+      </para>
+
       <remark role="help-description-end"/>
 
       <para>

@@ -577,12 +584,6 @@
       </itemizedlist>
 
       <para>
-        MySQL stores the <literal>sql_mode</literal> system variable
-        setting that is in effect at the time a routine is created, and
-        always executes the routine with this setting in force.
-      </para>
-
-      <para>
         When the routine is invoked, an implicit <literal>USE
         <replaceable>db_name</replaceable></literal> is performed (and
         undone when the routine terminates). <literal>USE</literal>


Modified: trunk/refman-5.0/triggers.xml
===================================================================
--- trunk/refman-5.0/triggers.xml	2007-01-11 18:34:26 UTC (rev 4457)
+++ trunk/refman-5.0/triggers.xml	2007-01-11 20:38:59 UTC (rev 4458)
Changed blocks: 2, Lines Added: 8, Lines Deleted: 1; 1022 bytes

@@ -49,7 +49,7 @@
     logging as it applies to triggers are given in
     <xref linkend="stored-procedure-logging"/>.
   </para>
-  
+
   <para>
     For answers to some common questions about triggers in MySQL
     &current-series;, see <xref linkend="faqs-triggers"/>.

@@ -197,6 +197,13 @@
     </para>
 
     <para>
+      MySQL stores the <literal>sql_mode</literal> system variable
+      setting that is in effect at the time a trigger is created, and
+      always executes the trigger with this setting in force,
+      <emphasis>regardless of the current server SQL mode</emphasis>.
+    </para>
+
+    <para>
       <emphasis role="bold">Note</emphasis>: Currently, triggers are not
       activated by cascaded foreign key actions. This limitation will be
       lifted as soon as possible.


Modified: trunk/refman-5.1/events.xml
===================================================================
--- trunk/refman-5.1/events.xml	2007-01-11 18:34:26 UTC (rev 4457)
+++ trunk/refman-5.1/events.xml	2007-01-11 20:38:59 UTC (rev 4458)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 786 bytes

@@ -931,6 +931,13 @@
 </programlisting>
 
       <para>
+        MySQL stores the <literal>sql_mode</literal> system variable
+        setting that is in effect at the time an event is created, and
+        always executes the event with this setting in force,
+        <emphasis>regardless of the current server SQL mode</emphasis>.
+      </para>
+
+      <para>
         A <literal>CREATE EVENT</literal> statement that contains an
         <literal>ALTER EVENT</literal> statement in its
         <literal>DO</literal> clause appears to succeed; however, when


Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml	2007-01-11 18:34:26 UTC (rev 4457)
+++ trunk/refman-5.1/stored-procedures.xml	2007-01-11 20:38:59 UTC (rev 4458)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 6; 1205 bytes

@@ -425,6 +425,13 @@
         <xref linkend="routine-restrictions"/>.
       </para>
 
+      <para>
+        MySQL stores the <literal>sql_mode</literal> system variable
+        setting that is in effect at the time a routine is created, and
+        always executes the routine with this setting in force,
+        <emphasis>regardless of the current server SQL mode</emphasis>.
+      </para>
+
       <remark role="help-description-end"/>
 
       <para>

@@ -571,12 +578,6 @@
       </itemizedlist>
 
       <para>
-        MySQL stores the <literal>sql_mode</literal> system variable
-        setting that is in effect at the time a routine is created, and
-        always executes the routine with this setting in force.
-      </para>
-
-      <para>
         When the routine is invoked, an implicit <literal>USE
         <replaceable>db_name</replaceable></literal> is performed (and
         undone when the routine terminates). <literal>USE</literal>


Modified: trunk/refman-5.1/triggers.xml
===================================================================
--- trunk/refman-5.1/triggers.xml	2007-01-11 18:34:26 UTC (rev 4457)
+++ trunk/refman-5.1/triggers.xml	2007-01-11 20:38:59 UTC (rev 4458)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 759 bytes

@@ -198,6 +198,13 @@
     </para>
 
     <para>
+      MySQL stores the <literal>sql_mode</literal> system variable
+      setting that is in effect at the time a trigger is created, and
+      always executes the trigger with this setting in force,
+      <emphasis>regardless of the current server SQL mode</emphasis>.
+    </para>
+
+    <para>
       <emphasis role="bold">Note</emphasis>: Currently, triggers are not
       activated by cascaded foreign key actions. This limitation will be
       lifted as soon as possible.