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

[paul]

Author: paul
Date: 2006-04-18 19:23:17 +0200 (Tue, 18 Apr 2006)
New Revision: 1857

Log:
 r6738@polar:  paul | 2006-04-18 12:23:24 -0500
 None of DROP TABLE, TRUNCATE, or dropping a partition activate
 DELETE triggers. (Bug#14351)


Modified:
   trunk/
   trunk/refman-5.0/triggers.xml
   trunk/refman-5.1/triggers.xml


Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6732
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9486
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4505
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:6738
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:9486
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4505

Modified: trunk/refman-5.0/triggers.xml
===================================================================
--- trunk/refman-5.0/triggers.xml	2006-04-18 16:22:07 UTC (rev 1856)
+++ trunk/refman-5.0/triggers.xml	2006-04-18 17:23:17 UTC (rev 1857)
@@ -139,9 +139,11 @@
           <literal>DELETE</literal>: The trigger is activated whenever a
           row is deleted from the table; for example, through
           <literal>DELETE</literal> and
<literal>REPLACE</literal>
-          statements. However, a <literal>TRUNCATE</literal> statement
-          on the table does <emphasis>not</emphasis> invoke this
-          trigger. See <xref linkend="truncate"/>.
+          statements. However, <literal>DROP TABLE</literal> and
+          <literal>TRUNCATE</literal> statements on the table do
+          <emphasis>not</emphasis> activate this trigger, because they
+          do not use <literal>DELETE</literal>. See
+          <xref linkend="truncate"/>.
         </para>
       </listitem>
 
@@ -536,12 +538,12 @@
      
(<literal><replaceable>table_name</replaceable>.<replaceable>trigger_name</replaceable></literal>).
       When upgrading from a previous version of MySQL 5.0 to MySQL
       5.0.10 or newer, you must drop all triggers <emphasis>before
-        upgrading</emphasis> and re-create them afterwards, or else
+      upgrading</emphasis> and re-create them afterwards, or else
       <literal>DROP TRIGGER</literal> does not work after the upgrade.
       See <xref linkend="upgrading-from-4-1"/>, for a suggested upgrade
       procedure.
     </para>
-    
+
     <para>
       In addition, triggers created in MySQL 5.0.16 or later cannot be
       dropped following a downgrade to MySQL 5.0.15 or earlier. If you
@@ -549,7 +551,7 @@
       all triggers <emphasis>prior to</emphasis> the downgrade, and then
       re-create them afterwards.
     </para>
-    
+
     <para>
       (For more information about these two issues, see Bug #15921 and
       Bug #18588.)

Modified: trunk/refman-5.1/triggers.xml
===================================================================
--- trunk/refman-5.1/triggers.xml	2006-04-18 16:22:07 UTC (rev 1856)
+++ trunk/refman-5.1/triggers.xml	2006-04-18 17:23:17 UTC (rev 1857)
@@ -139,9 +139,12 @@
           <literal>DELETE</literal>: The trigger is activated whenever a
           row is deleted from the table; for example, through
           <literal>DELETE</literal> and
<literal>REPLACE</literal>
-          statements. However, a <literal>TRUNCATE</literal> statement
-          on the table does <emphasis>not</emphasis> invoke this
-          trigger. See <xref linkend="truncate"/>.
+          statements. However, <literal>DROP TABLE</literal> and
+          <literal>TRUNCATE</literal> statements on the table do
+          <emphasis>not</emphasis> activate this trigger, because they
+          do not use <literal>DELETE</literal>. Dropping a partition
+          does not activate <literal>DELETE</literal> triggers, either.
+          See <xref linkend="truncate"/>.
         </para>
       </listitem>