Author: jstephens
Date: 2006-03-30 06:03:17 +0200 (Thu, 30 Mar 2006)
New Revision: 1701
Log:
Oopsie! Last commit added info to a section of TRUNCATE beginning with "for
other storage engines" which made it sound like the limitation didn't apply to
InnoDB when in fact it applies to all storage engines. (Moved the new para.)
Modified:
trunk/refman-5.1/sql-syntax.xml
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-03-30 03:57:18 UTC (rev 1700)
+++ trunk/refman-5.1/sql-syntax.xml 2006-03-30 04:03:17 UTC (rev 1701)
@@ -10471,13 +10471,6 @@
Truncate operations drop and re-create the table, which is
much faster than deleting rows one by one.
</para>
-
- <para>
- Since truncation of a table does not make any use of
- <literal>DELETE</literal>, the <literal>TRUNCATE</literal>
- statement does not invoke <literal>ON DELETE</literal>
- triggers.
- </para>
</listitem>
<listitem>
@@ -10525,6 +10518,13 @@
</listitem>
</itemizedlist>
+
+ <para>
+ Since truncation of a table does not make any use of
+ <literal>DELETE</literal>, the <literal>TRUNCATE</literal>
+ statement does not invoke <literal>ON DELETE</literal>
+ triggers.
+ </para>
<para>
<literal>TRUNCATE TABLE</literal> is an Oracle SQL extension
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1701 - trunk/refman-5.1 | jon | 30 Mar |