Author: jstephens
Date: 2007-09-03 22:19:34 +0200 (Mon, 03 Sep 2007)
New Revision: 7639
Log:
Triggers are activated by SQL statements only. (Geert/Support request)
Modified:
trunk/refman-5.0/restrictions.xml
trunk/refman-5.0/triggers.xml
trunk/refman-5.1/triggers.xml
trunk/refman-5.2/triggers.xml
Modified: trunk/refman-5.0/restrictions.xml
===================================================================
--- trunk/refman-5.0/restrictions.xml 2007-09-03 16:25:24 UTC (rev 7638)
+++ trunk/refman-5.0/restrictions.xml 2007-09-03 20:19:34 UTC (rev 7639)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 2; 714 bytes
@@ -59,9 +59,13 @@
<para>
The table-maintenance statements <literal>CHECK
TABLES</literal> and <literal>OPTIMIZE TABLES</literal>.
- <emphasis role="bold">Note</emphasis>: This restriction is
- lifted beginning with MySQL 5.0.17.
</para>
+
+ <note>
+ <para>
+ This restriction is lifted beginning with MySQL 5.0.17.
+ </para>
+ </note>
</listitem>
<listitem>
Modified: trunk/refman-5.0/triggers.xml
===================================================================
--- trunk/refman-5.0/triggers.xml 2007-09-03 16:25:24 UTC (rev 7638)
+++ trunk/refman-5.0/triggers.xml 2007-09-03 20:19:34 UTC (rev 7639)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 1411 bytes
@@ -37,6 +37,16 @@
Query OK, 0 rows affected (0.06 sec)
</programlisting>
+ <important>
+ <para>
+ MySQL triggers are activated by SQL statements
+ <emphasis>only</emphasis>. They are not activated by changes in
+ tables made by APIs that do not transmit SQL statements to the
+ MySQL Server; in particular, they are not activated by updates
+ made using the <literal>NDB</literal> API.
+ </para>
+ </important>
+
<para>
This chapter describes the syntax for creating and dropping
triggers, and shows some examples of how to use them. Discussion of
@@ -618,6 +628,16 @@
that is updated.
</para>
+ <important>
+ <para>
+ MySQL triggers are activated by SQL statements
+ <emphasis>only</emphasis>. They are not activated by changes in
+ tables made by APIs that do not transmit SQL statements to the
+ MySQL Server; in particular, they are not activated by updates
+ made using the <literal>NDB</literal> API.
+ </para>
+ </important>
+
<para>
To create a trigger or drop a trigger, use the <literal>CREATE
TRIGGER</literal> or <literal>DROP TRIGGER</literal> statement.
Modified: trunk/refman-5.1/triggers.xml
===================================================================
--- trunk/refman-5.1/triggers.xml 2007-09-03 16:25:24 UTC (rev 7638)
+++ trunk/refman-5.1/triggers.xml 2007-09-03 20:19:34 UTC (rev 7639)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 1411 bytes
@@ -36,6 +36,16 @@
Query OK, 0 rows affected (0.06 sec)
</programlisting>
+ <important>
+ <para>
+ MySQL triggers are activated by SQL statements
+ <emphasis>only</emphasis>. They are not activated by changes in
+ tables made by APIs that do not transmit SQL statements to the
+ MySQL Server; in particular, they are not activated by updates
+ made using the <literal>NDB</literal> API.
+ </para>
+ </important>
+
<para>
This chapter describes the syntax for creating and dropping
triggers, and shows some examples of how to use them. Discussion of
@@ -569,6 +579,16 @@
that is updated.
</para>
+ <important>
+ <para>
+ MySQL triggers are activated by SQL statements
+ <emphasis>only</emphasis>. They are not activated by changes in
+ tables made by APIs that do not transmit SQL statements to the
+ MySQL Server; in particular, they are not activated by updates
+ made using the <literal>NDB</literal> API.
+ </para>
+ </important>
+
<para>
To create a trigger or drop a trigger, use the <literal>CREATE
TRIGGER</literal> or <literal>DROP TRIGGER</literal> statement.
Modified: trunk/refman-5.2/triggers.xml
===================================================================
--- trunk/refman-5.2/triggers.xml 2007-09-03 16:25:24 UTC (rev 7638)
+++ trunk/refman-5.2/triggers.xml 2007-09-03 20:19:34 UTC (rev 7639)
Changed blocks: 2, Lines Added: 20, Lines Deleted: 0; 1411 bytes
@@ -36,6 +36,16 @@
Query OK, 0 rows affected (0.06 sec)
</programlisting>
+ <important>
+ <para>
+ MySQL triggers are activated by SQL statements
+ <emphasis>only</emphasis>. They are not activated by changes in
+ tables made by APIs that do not transmit SQL statements to the
+ MySQL Server; in particular, they are not activated by updates
+ made using the <literal>NDB</literal> API.
+ </para>
+ </important>
+
<para>
This chapter describes the syntax for creating and dropping
triggers, and shows some examples of how to use them. Discussion of
@@ -569,6 +579,16 @@
that is updated.
</para>
+ <important>
+ <para>
+ MySQL triggers are activated by SQL statements
+ <emphasis>only</emphasis>. They are not activated by changes in
+ tables made by APIs that do not transmit SQL statements to the
+ MySQL Server; in particular, they are not activated by updates
+ made using the <literal>NDB</literal> API.
+ </para>
+ </important>
+
<para>
To create a trigger or drop a trigger, use the <literal>CREATE
TRIGGER</literal> or <literal>DROP TRIGGER</literal> statement.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7639 - in trunk: refman-5.0 refman-5.1 refman-5.2 | jon | 3 Sep |
