Author: paul
Date: 2008-05-14 03:45:04 +0200 (Wed, 14 May 2008)
New Revision: 10731
Log:
r31353@frost: paul | 2008-05-13 16:51:59 -0500
log_bin_trust_function_creators also applies to trigger creation
Modified:
trunk/it/refman-5.1/dba-core.xml
trunk/it/refman-5.1/faqs.xml
trunk/it/refman-5.1/stored-procedures.xml
trunk/pt/refman-5.1/dba-core.xml
trunk/pt/refman-5.1/faqs.xml
trunk/pt/refman-5.1/stored-procedures.xml
trunk/refman-5.0/dba-core.xml
trunk/refman-5.0/faqs.xml
trunk/refman-5.0/stored-procedures.xml
trunk/refman-5.1/dba-core.xml
trunk/refman-5.1/faqs.xml
trunk/refman-5.1/stored-procedures.xml
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/faqs.xml
trunk/refman-6.0/stored-procedures.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31339
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31263
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31353
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31263
Modified: trunk/it/refman-5.1/dba-core.xml
===================================================================
--- trunk/it/refman-5.1/dba-core.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/it/refman-5.1/dba-core.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 4; 1852 bytes
@@ -1485,8 +1485,9 @@
variable to 1. With an argument of 0, this option sets the
system variable to 0.
<literal>log_bin_trust_function_creators</literal> affects
- how MySQL enforces restrictions on stored function creation.
- See <xref linkend="stored-procedure-logging"/>.
+ how MySQL enforces restrictions on stored function and
+ trigger creation. See
+ <xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
@@ -5430,7 +5431,7 @@
controls whether stored function creators can be trusted not
to create stored functions that will cause unsafe events to
be written to the binary log. If set to 0 (the default),
- users are not allowed to create or alter stored routines
+ users are not allowed to create or alter stored functions
unless they have the <literal>SUPER</literal> privilege in
addition to the <literal>CREATE ROUTINE</literal> or
<literal>ALTER ROUTINE</literal> privilege. A setting of 0
@@ -5439,7 +5440,8 @@
characteristic, or with the <literal>READS SQL
DATA</literal> or <literal>NO SQL</literal> characteristic.
If the variable is set to 1, MySQL does not enforce these
- restrictions on stored function creation. See
+ restrictions on stored function creation. This variable also
+ applies to trigger creation. See
<xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
Modified: trunk/it/refman-5.1/faqs.xml
===================================================================
--- trunk/it/refman-5.1/faqs.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/it/refman-5.1/faqs.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 543 bytes
@@ -872,7 +872,8 @@
<para>
A stored procedure can execute an SQL statement, such as an
- <literal>UPDATE</literal>, that causes a trigger to fire.
+ <literal>UPDATE</literal>, that causes a trigger to
+ activate.
</para>
</answer>
Modified: trunk/it/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/it/refman-5.1/stored-procedures.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/it/refman-5.1/stored-procedures.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 7; 1356 bytes
@@ -2615,13 +2615,10 @@
<para>
Triggers are similar to stored functions, so the preceding remarks
regarding functions also apply to triggers with the following
- exceptions: <literal>log_bin_trust_function_creators</literal>
- does not apply to triggers and does not affect the privileges
- required for <literal>CREATE TRIGGER</literal>. Also,
- <literal>CREATE TRIGGER</literal> does not have an optional
- <literal>DETERMINISTIC</literal> characteristic, so triggers are
- assumed to be always deterministic. However, this assumption might
- in some cases be invalid. For example, the
+ exception: <literal>CREATE TRIGGER</literal> does not have an
+ optional <literal>DETERMINISTIC</literal> characteristic, so
+ triggers are assumed to be always deterministic. However, this
+ assumption might in some cases be invalid. For example, the
<function role="sql">UUID()</function> function is
non-deterministic (and does not replicate). You should be careful
about using such functions in triggers.
Modified: trunk/pt/refman-5.1/dba-core.xml
===================================================================
--- trunk/pt/refman-5.1/dba-core.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/pt/refman-5.1/dba-core.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 4; 1852 bytes
@@ -1485,8 +1485,9 @@
variable to 1. With an argument of 0, this option sets the
system variable to 0.
<literal>log_bin_trust_function_creators</literal> affects
- how MySQL enforces restrictions on stored function creation.
- See <xref linkend="stored-procedure-logging"/>.
+ how MySQL enforces restrictions on stored function and
+ trigger creation. See
+ <xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
@@ -5430,7 +5431,7 @@
controls whether stored function creators can be trusted not
to create stored functions that will cause unsafe events to
be written to the binary log. If set to 0 (the default),
- users are not allowed to create or alter stored routines
+ users are not allowed to create or alter stored functions
unless they have the <literal>SUPER</literal> privilege in
addition to the <literal>CREATE ROUTINE</literal> or
<literal>ALTER ROUTINE</literal> privilege. A setting of 0
@@ -5439,7 +5440,8 @@
characteristic, or with the <literal>READS SQL
DATA</literal> or <literal>NO SQL</literal> characteristic.
If the variable is set to 1, MySQL does not enforce these
- restrictions on stored function creation. See
+ restrictions on stored function creation. This variable also
+ applies to trigger creation. See
<xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
Modified: trunk/pt/refman-5.1/faqs.xml
===================================================================
--- trunk/pt/refman-5.1/faqs.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/pt/refman-5.1/faqs.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 543 bytes
@@ -872,7 +872,8 @@
<para>
A stored procedure can execute an SQL statement, such as an
- <literal>UPDATE</literal>, that causes a trigger to fire.
+ <literal>UPDATE</literal>, that causes a trigger to
+ activate.
</para>
</answer>
Modified: trunk/pt/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/pt/refman-5.1/stored-procedures.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/pt/refman-5.1/stored-procedures.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 7; 1356 bytes
@@ -2615,13 +2615,10 @@
<para>
Triggers are similar to stored functions, so the preceding remarks
regarding functions also apply to triggers with the following
- exceptions: <literal>log_bin_trust_function_creators</literal>
- does not apply to triggers and does not affect the privileges
- required for <literal>CREATE TRIGGER</literal>. Also,
- <literal>CREATE TRIGGER</literal> does not have an optional
- <literal>DETERMINISTIC</literal> characteristic, so triggers are
- assumed to be always deterministic. However, this assumption might
- in some cases be invalid. For example, the
+ exception: <literal>CREATE TRIGGER</literal> does not have an
+ optional <literal>DETERMINISTIC</literal> characteristic, so
+ triggers are assumed to be always deterministic. However, this
+ assumption might in some cases be invalid. For example, the
<function role="sql">UUID()</function> function is
non-deterministic (and does not replicate). You should be careful
about using such functions in triggers.
Modified: trunk/refman-5.0/dba-core.xml
===================================================================
--- trunk/refman-5.0/dba-core.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-5.0/dba-core.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 3; 1240 bytes
@@ -1383,8 +1383,9 @@
variable to 1. With an argument of 0, this option sets the
system variable to 0.
<literal>log_bin_trust_function_creators</literal> affects
- how MySQL enforces restrictions on stored function creation.
- See <xref linkend="stored-procedure-logging"/>.
+ how MySQL enforces restrictions on stored function and
+ trigger creation. See
+ <xref linkend="stored-procedure-logging"/>.
</para>
<para>
@@ -5192,7 +5193,8 @@
characteristic, or with the <literal>READS SQL
DATA</literal> or <literal>NO SQL</literal> characteristic.
If the variable is set to 1, MySQL does not enforce these
- restrictions on stored function creation. See
+ restrictions on stored function creation. This variable also
+ applies to trigger creation. See
<xref linkend="stored-procedure-logging"/>.
</para>
Modified: trunk/refman-5.0/faqs.xml
===================================================================
--- trunk/refman-5.0/faqs.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-5.0/faqs.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 534 bytes
@@ -856,7 +856,8 @@
<para>
A stored procedure can execute an SQL statement, such as an
- <literal>UPDATE</literal>, that causes a trigger to fire.
+ <literal>UPDATE</literal>, that causes a trigger to
+ activate.
</para>
</answer>
Modified: trunk/refman-5.0/stored-procedures.xml
===================================================================
--- trunk/refman-5.0/stored-procedures.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-5.0/stored-procedures.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 7; 1347 bytes
@@ -2874,13 +2874,10 @@
<para>
Triggers are similar to stored functions, so the preceding remarks
regarding functions also apply to triggers with the following
- exceptions: <literal>log_bin_trust_function_creators</literal>
- does not apply to triggers and does not affect the privileges
- required for <literal>CREATE TRIGGER</literal>. Also,
- <literal>CREATE TRIGGER</literal> does not have an optional
- <literal>DETERMINISTIC</literal> characteristic, so triggers are
- assumed to be always deterministic. However, this assumption might
- in some cases be invalid. For example, the
+ exception: <literal>CREATE TRIGGER</literal> does not have an
+ optional <literal>DETERMINISTIC</literal> characteristic, so
+ triggers are assumed to be always deterministic. However, this
+ assumption might in some cases be invalid. For example, the
<function role="sql">UUID()</function> function is
non-deterministic (and does not replicate). You should be careful
about using such functions in triggers.
Modified: trunk/refman-5.1/dba-core.xml
===================================================================
--- trunk/refman-5.1/dba-core.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-5.1/dba-core.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 4; 1843 bytes
@@ -1485,8 +1485,9 @@
variable to 1. With an argument of 0, this option sets the
system variable to 0.
<literal>log_bin_trust_function_creators</literal> affects
- how MySQL enforces restrictions on stored function creation.
- See <xref linkend="stored-procedure-logging"/>.
+ how MySQL enforces restrictions on stored function and
+ trigger creation. See
+ <xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
@@ -5430,7 +5431,7 @@
controls whether stored function creators can be trusted not
to create stored functions that will cause unsafe events to
be written to the binary log. If set to 0 (the default),
- users are not allowed to create or alter stored routines
+ users are not allowed to create or alter stored functions
unless they have the <literal>SUPER</literal> privilege in
addition to the <literal>CREATE ROUTINE</literal> or
<literal>ALTER ROUTINE</literal> privilege. A setting of 0
@@ -5439,7 +5440,8 @@
characteristic, or with the <literal>READS SQL
DATA</literal> or <literal>NO SQL</literal> characteristic.
If the variable is set to 1, MySQL does not enforce these
- restrictions on stored function creation. See
+ restrictions on stored function creation. This variable also
+ applies to trigger creation. See
<xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
Modified: trunk/refman-5.1/faqs.xml
===================================================================
--- trunk/refman-5.1/faqs.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-5.1/faqs.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 534 bytes
@@ -872,7 +872,8 @@
<para>
A stored procedure can execute an SQL statement, such as an
- <literal>UPDATE</literal>, that causes a trigger to fire.
+ <literal>UPDATE</literal>, that causes a trigger to
+ activate.
</para>
</answer>
Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-5.1/stored-procedures.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 7; 1347 bytes
@@ -2684,13 +2684,10 @@
<para>
Triggers are similar to stored functions, so the preceding remarks
regarding functions also apply to triggers with the following
- exceptions: <literal>log_bin_trust_function_creators</literal>
- does not apply to triggers and does not affect the privileges
- required for <literal>CREATE TRIGGER</literal>. Also,
- <literal>CREATE TRIGGER</literal> does not have an optional
- <literal>DETERMINISTIC</literal> characteristic, so triggers are
- assumed to be always deterministic. However, this assumption might
- in some cases be invalid. For example, the
+ exception: <literal>CREATE TRIGGER</literal> does not have an
+ optional <literal>DETERMINISTIC</literal> characteristic, so
+ triggers are assumed to be always deterministic. However, this
+ assumption might in some cases be invalid. For example, the
<function role="sql">UUID()</function> function is
non-deterministic (and does not replicate). You should be careful
about using such functions in triggers.
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-6.0/dba-core.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 3, Lines Added: 6, Lines Deleted: 4; 1843 bytes
@@ -1464,8 +1464,9 @@
variable to 1. With an argument of 0, this option sets the
system variable to 0.
<literal>log_bin_trust_function_creators</literal> affects
- how MySQL enforces restrictions on stored function creation.
- See <xref linkend="stored-procedure-logging"/>.
+ how MySQL enforces restrictions on stored function and
+ trigger creation. See
+ <xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
@@ -5322,7 +5323,7 @@
controls whether stored function creators can be trusted not
to create stored functions that will cause unsafe events to
be written to the binary log. If set to 0 (the default),
- users are not allowed to create or alter stored routines
+ users are not allowed to create or alter stored functions
unless they have the <literal>SUPER</literal> privilege in
addition to the <literal>CREATE ROUTINE</literal> or
<literal>ALTER ROUTINE</literal> privilege. A setting of 0
@@ -5331,7 +5332,8 @@
characteristic, or with the <literal>READS SQL
DATA</literal> or <literal>NO SQL</literal> characteristic.
If the variable is set to 1, MySQL does not enforce these
- restrictions on stored function creation. See
+ restrictions on stored function creation. This variable also
+ applies to trigger creation. See
<xref linkend="stored-procedure-logging"/>.
</para>
</listitem>
Modified: trunk/refman-6.0/faqs.xml
===================================================================
--- trunk/refman-6.0/faqs.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-6.0/faqs.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 1; 534 bytes
@@ -877,7 +877,8 @@
<para>
A stored procedure can execute an SQL statement, such as an
- <literal>UPDATE</literal>, that causes a trigger to fire.
+ <literal>UPDATE</literal>, that causes a trigger to
+ activate.
</para>
</answer>
Modified: trunk/refman-6.0/stored-procedures.xml
===================================================================
--- trunk/refman-6.0/stored-procedures.xml 2008-05-14 01:43:16 UTC (rev 10730)
+++ trunk/refman-6.0/stored-procedures.xml 2008-05-14 01:45:04 UTC (rev 10731)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 7; 1347 bytes
@@ -2682,13 +2682,10 @@
<para>
Triggers are similar to stored functions, so the preceding remarks
regarding functions also apply to triggers with the following
- exceptions: <literal>log_bin_trust_function_creators</literal>
- does not apply to triggers and does not affect the privileges
- required for <literal>CREATE TRIGGER</literal>. Also,
- <literal>CREATE TRIGGER</literal> does not have an optional
- <literal>DETERMINISTIC</literal> characteristic, so triggers are
- assumed to be always deterministic. However, this assumption might
- in some cases be invalid. For example, the
+ exception: <literal>CREATE TRIGGER</literal> does not have an
+ optional <literal>DETERMINISTIC</literal> characteristic, so
+ triggers are assumed to be always deterministic. However, this
+ assumption might in some cases be invalid. For example, the
<function role="sql">UUID()</function> function is
non-deterministic (and does not replicate). You should be careful
about using such functions in triggers.
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10731 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-5.0 refman-5.1 refman-6.0 | paul | 14 May |
