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

[paul]

Author: paul
Date: 2008-02-21 22:30:30 +0100 (Thu, 21 Feb 2008)
New Revision: 9968

Log:
 r29421@frost:  paul | 2008-02-21 15:26:47 -0600
 log_bin_trust_function_creators does not apply to triggers. (Dmitri)
 (Bug#34729)


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

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34985
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29397
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29525
   + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:34985
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:29421
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:29525


Modified: trunk/refman-5.0/stored-procedures.xml
===================================================================
--- trunk/refman-5.0/stored-procedures.xml	2008-02-21 15:42:40 UTC (rev 9967)
+++ trunk/refman-5.0/stored-procedures.xml	2008-02-21 21:30:30 UTC (rev 9968)
Changed blocks: 1, Lines Added: 13, Lines Deleted: 9; 2056 bytes

@@ -2751,21 +2751,25 @@
     <para>
       Triggers are similar to stored functions, so the preceding remarks
       regarding functions also apply to triggers with the following
-      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
+      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
       <function role="sql">UUID()</function> function is
       non-deterministic (and does not replicate). You should be careful
       about using such functions in triggers.
     </para>
 
     <para>
-      Triggers can update tables (as of MySQL 5.0.10), so error messages
-      similar to those for stored functions occur with <literal>CREATE
-      TRIGGER</literal> if you do not have the <literal>SUPER</literal>
-      privilege and <literal>log_bin_trust_function_creators</literal>
-      is 0.
+      Triggers can update tables, so error messages similar to those for
+      stored functions occur with <literal>CREATE TRIGGER</literal> if
+      you do not have the required privileges. On the slave side, the
+      slave uses the trigger <literal>DEFINER</literal> attribute to
+      determine which user is considered to be the creator of the
+      trigger.
     </para>
 
     <para>


Modified: trunk/refman-5.1/stored-procedures.xml
===================================================================
--- trunk/refman-5.1/stored-procedures.xml	2008-02-21 15:42:40 UTC (rev 9967)
+++ trunk/refman-5.1/stored-procedures.xml	2008-02-21 21:30:30 UTC (rev 9968)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 10; 2124 bytes

@@ -2562,10 +2562,13 @@
     <para>
       Triggers are similar to stored functions, so the preceding remarks
       regarding functions also apply to triggers with the following
-      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
+      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
       <function role="sql">UUID()</function> function is
       non-deterministic (and does not replicate). You should be careful
       about using such functions in triggers.

@@ -2574,12 +2577,10 @@
     <para>
       Triggers can update tables, so error messages similar to those for
       stored functions occur with <literal>CREATE TRIGGER</literal> if
-      you do not have the <literal>TRIGGER</literal> privilege
-      (<literal>SUPER</literal> before MySQL 5.1.6) and
-      <literal>log_bin_trust_function_creators</literal> is 0. (On the
-      slave side, the slave uses the trigger <literal>DEFINER</literal>
-      attribute to determine which user is considered to be the creator
-      of the trigger.)
+      you do not have the required privileges. On the slave side, the
+      slave uses the trigger <literal>DEFINER</literal> attribute to
+      determine which user is considered to be the creator of the
+      trigger.
     </para>
 
     <para>


Modified: trunk/refman-6.0/stored-procedures.xml
===================================================================
--- trunk/refman-6.0/stored-procedures.xml	2008-02-21 15:42:40 UTC (rev 9967)
+++ trunk/refman-6.0/stored-procedures.xml	2008-02-21 21:30:30 UTC (rev 9968)
Changed blocks: 2, Lines Added: 11, Lines Deleted: 10; 2124 bytes

@@ -2540,10 +2540,13 @@
     <para>
       Triggers are similar to stored functions, so the preceding remarks
       regarding functions also apply to triggers with the following
-      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
+      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
       <function role="sql">UUID()</function> function is
       non-deterministic (and does not replicate). You should be careful
       about using such functions in triggers.

@@ -2552,12 +2555,10 @@
     <para>
       Triggers can update tables, so error messages similar to those for
       stored functions occur with <literal>CREATE TRIGGER</literal> if
-      you do not have the <literal>TRIGGER</literal> privilege
-      (<literal>SUPER</literal> before MySQL 5.1.6) and
-      <literal>log_bin_trust_function_creators</literal> is 0. (On the
-      slave side, the slave uses the trigger <literal>DEFINER</literal>
-      attribute to determine which user is considered to be the creator
-      of the trigger.)
+      you do not have the required privileges. On the slave side, the
+      slave uses the trigger <literal>DEFINER</literal> attribute to
+      determine which user is considered to be the creator of the
+      trigger.
     </para>
 
     <para>