MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:jon.stephens Date:January 7 2011 11:46pm
Subject:svn commit - mysqldoc@docsrva: r24741 - in trunk: refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0
View as plain text  
Author: jstephens
Date: 2011-01-08 00:46:22 +0100 (Sat, 08 Jan 2011)
New Revision: 24741

Log:

Re-fxies Docs BUG#48510 (Thanks, Davi and Paul!)



Modified:
   trunk/refman-5.0/dba-mysqld-server-core.xml
   trunk/refman-5.0/dba-user-management-core.xml
   trunk/refman-5.0/functions-core.xml
   trunk/refman-5.0/replication-notes.xml
   trunk/refman-5.0/sql-syntax-server-administration.xml
   trunk/refman-5.1/dba-mysqld-server-core.xml
   trunk/refman-5.1/dba-user-management-core.xml
   trunk/refman-5.1/functions-core.xml
   trunk/refman-5.1/replication-notes.xml
   trunk/refman-5.1/sql-syntax-server-administration.xml
   trunk/refman-5.5/dba-mysqld-server-core.xml
   trunk/refman-5.5/dba-user-management-core.xml
   trunk/refman-5.5/replication-notes.xml
   trunk/refman-5.5/sql-syntax-server-administration.xml
   trunk/refman-5.6/dba-mysqld-server-core.xml
   trunk/refman-5.6/dba-user-management-core.xml
   trunk/refman-5.6/replication-notes.xml
   trunk/refman-5.6/sql-syntax-server-administration.xml
   trunk/refman-6.0/dba-mysqld-server-core.xml
   trunk/refman-6.0/dba-user-management-core.xml
   trunk/refman-6.0/replication-notes.xml
   trunk/refman-6.0/sql-syntax-server-administration.xml


Modified: trunk/refman-5.0/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.0/dba-mysqld-server-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.0/dba-mysqld-server-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 9, Lines Deleted: 9; 1725 bytes

@@ -8029,15 +8029,15 @@
           <para>
             In MySQL 5.0, enabling <literal>read_only</literal> does
             <emphasis>not</emphasis> prevent the use of the
-            <literal role="func">PASSWORD()</literal> function. This is
-            not necessarily the case for all MySQL release series. When
-            replicating from one MySQL release series to another (for
-            example, from a MySQL 5.0 master to a MySQL 5.1 slave), you
-            should check the documentation for the versions running on
-            both master and slave to determine whether the behavior of
-            <literal>read_only</literal> in this regard is or is not the
-            same, and, if it is different, whether this has an impact on
-            your applications.
+            <literal role="stmt">SET PASSWORD</literal> statement. This
+            is not necessarily the case for all MySQL release series.
+            When replicating from one MySQL release series to another
+            (for example, from a MySQL 5.0 master to a MySQL 5.1 slave),
+            you should check the documentation for the versions running
+            on both master and slave to determine whether the behavior
+            of <literal>read_only</literal> in this regard is or is not
+            the same, and, if it is different, whether this has an
+            impact on your applications.
           </para>
         </important>
       </listitem>


Modified: trunk/refman-5.0/dba-user-management-core.xml
===================================================================
--- trunk/refman-5.0/dba-user-management-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.0/dba-user-management-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 7; 643 bytes

@@ -1257,13 +1257,6 @@
 
     </itemizedlist>
 
-    <para>
-      In MySQL 5.0, enabling the
-      <literal role="sysvar">read_only</literal> system variable does
-      not prevent use of the <literal role="func">PASSWORD()</literal>
-      function.
-    </para>
-
     <note>
       <para>
         <literal role="func">PASSWORD()</literal> encryption differs


Modified: trunk/refman-5.0/functions-core.xml
===================================================================
--- trunk/refman-5.0/functions-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.0/functions-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 7; 697 bytes

@@ -15207,13 +15207,6 @@
           encrypted. See <literal role="func">ENCRYPT()</literal>.
         </para>
 
-        <para>
-          In MySQL 5.0, enabling the
-          <literal role="sysvar">read_only</literal> system variable
-          does not prevent use of
-          <literal role="func">PASSWORD()</literal>.
-        </para>
-
         <note>
           <para>
             The <literal role="func">PASSWORD()</literal> function is


Modified: trunk/refman-5.0/replication-notes.xml
===================================================================
--- trunk/refman-5.0/replication-notes.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.0/replication-notes.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 5; 1227 bytes

@@ -1789,17 +1789,18 @@
       </para>
 
       <para>
-        The <literal role="sysvar">storage_engine</literal> system
-        variable is not replicated, which is a good thing for
-        replication between different storage engines.
+        The <literal role="sysvar">storage_engine</literal> system variable
+        is not replicated, regardless of the logging mode; this is
+        intended to facilitate replication between different storage
+        engines.
       </para>
 
       <para>
         The <literal role="sysvar">read_only</literal> system variable
         is not replicated. In addition, the enabling this variable has
         different effects with regard to temporary tables, table
-        locking, and the <literal role="func">PASSWORD()</literal>
-        function in different MySQL versions.
+        locking, and the <literal role="stmt">SET PASSWORD</literal>
+        statement in different MySQL versions.
       </para>
 
       <para>


Modified: trunk/refman-5.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.0/sql-syntax-server-administration.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.0/sql-syntax-server-administration.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 0; 772 bytes

@@ -1903,6 +1903,12 @@
       </para>
 
       <para>
+        In MySQL 5.0, enabling the
+        <literal role="sysvar">read_only</literal> system variable does
+        not prevent use of <literal>SET PASSWORD</literal>.
+      </para>
+
+      <para>
         With a <literal>FOR</literal> clause, this statement sets the
         password for a specific account on the current server host. Only
         clients that have the <literal role="stmt">UPDATE</literal>


Modified: trunk/refman-5.1/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.1/dba-mysqld-server-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.1/dba-mysqld-server-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 10, Lines Deleted: 9; 1789 bytes

@@ -8891,15 +8891,16 @@
 
         <important>
           <para>
-            In MySQL 5.1, enabling <literal>read_only</literal> prevents
-            the use of the <literal role="func">PASSWORD()</literal>
-            function by any user not having the
-            <literal role="priv">SUPER</literal> privilege. This is not
-            necessarily the case for all MySQL release series. When
-            replicating from one MySQL release series to another (for
-            example, from a MySQL 5.0 master to a MySQL 5.1 slave), you
-            should check the documentation for the versions running on
-            both master and slave to determine whether the behavior of
+            In MySQL &current-series;, enabling
+            <literal>read_only</literal> prevents the use of the
+            <literal role="stmt">SET PASSWORD</literal> statement by any
+            user not having the <literal role="priv">SUPER</literal>
+            privilege. This is not necessarily the case for all MySQL
+            release series. When replicating from one MySQL release
+            series to another (for example, from a MySQL 5.0 master to a
+            MySQL 5.1 or later slave), you should check the
+            documentation for the versions running on both master and
+            slave to determine whether the behavior of
             <literal>read_only</literal> in this regard is or is not the
             same, and, if it is different, whether this has an impact on
             your applications.


Modified: trunk/refman-5.1/dba-user-management-core.xml
===================================================================
--- trunk/refman-5.1/dba-user-management-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.1/dba-user-management-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 789 bytes

@@ -1258,10 +1258,10 @@
     </itemizedlist>
 
     <para>
-      In MySQL 5.1, enabling the
+      In MySQL &current-series;, enabling the
       <literal role="sysvar">read_only</literal> system variable
-      prevents the use of the <literal role="func">PASSWORD()</literal>
-      function by any user not having the
+      prevents the use of the <literal role="stmt">SET
+      PASSWORD</literal> statement by any user not having the
       <literal role="priv">SUPER</literal> privilege.
     </para>
 


Modified: trunk/refman-5.1/functions-core.xml
===================================================================
--- trunk/refman-5.1/functions-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.1/functions-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 0, Lines Deleted: 7; 761 bytes

@@ -16534,13 +16534,6 @@
           encrypted. See <literal role="func">ENCRYPT()</literal>.
         </para>
 
-        <para>
-          In MySQL 5.1 and later, when the
-          <literal role="sysvar">read_only</literal> system variable is
-          enabled, the <literal role="priv">SUPER</literal> privilege is
-          required to use <literal role="func">PASSWORD()</literal>.
-        </para>
-
         <note>
           <para>
             The <literal role="func">PASSWORD()</literal> function is


Modified: trunk/refman-5.1/replication-notes.xml
===================================================================
--- trunk/refman-5.1/replication-notes.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.1/replication-notes.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 756 bytes

@@ -3770,8 +3770,8 @@
         The <literal role="sysvar">read_only</literal> system variable
         is not replicated. In addition, the enabling this variable has
         different effects with regard to temporary tables, table
-        locking, and the <literal role="func">PASSWORD()</literal>
-        function in different MySQL versions.
+        locking, and the <literal role="stmt">SET PASSWORD</literal>
+        statement in different MySQL versions.
       </para>
 
       <para>


Modified: trunk/refman-5.1/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.1/sql-syntax-server-administration.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.1/sql-syntax-server-administration.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 856 bytes

@@ -1840,6 +1840,13 @@
       </para>
 
       <para>
+        In MySQL 5.1 and later, when the
+        <literal role="sysvar">read_only</literal> system variable is
+        enabled, the <literal role="priv">SUPER</literal> privilege is
+        required to use <literal role="stmt">SET PASSWORD</literal>.
+      </para>
+
+      <para>
         With a <literal>FOR</literal> clause, this statement sets the
         password for a specific account on the current server host. Only
         clients that have the <literal role="stmt">UPDATE</literal>


Modified: trunk/refman-5.5/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.5/dba-mysqld-server-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.5/dba-mysqld-server-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 18, Lines Deleted: 0; 1321 bytes

@@ -8868,6 +8868,24 @@
           master.
         </para>
 
+        <important>
+          <para>
+            In MySQL &current-series;, enabling
+            <literal>read_only</literal> prevents the use of the
+            <literal role="stmt">SET PASSWORD</literal> statement by any
+            user not having the <literal role="priv">SUPER</literal>
+            privilege. This is not necessarily the case for all MySQL
+            release series. When replicating from one MySQL release
+            series to another (for example, from a MySQL 5.0 master to a
+            MySQL 5.1 or later slave), you should check the
+            documentation for the versions running on both master and
+            slave to determine whether the behavior of
+            <literal>read_only</literal> in this regard is or is not the
+            same, and, if it is different, whether this has an impact on
+            your applications.
+          </para>
+        </important>
+
         <para>
           The following conditions apply:
         </para>


Modified: trunk/refman-5.5/dba-user-management-core.xml
===================================================================
--- trunk/refman-5.5/dba-user-management-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.5/dba-user-management-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 735 bytes

@@ -1268,6 +1268,14 @@
 
     </itemizedlist>
 
+    <para>
+      In MySQL &current-series;, enabling the
+      <literal role="sysvar">read_only</literal> system variable
+      prevents the use of the <literal role="stmt">SET
+      PASSWORD</literal> statement by any user not having the
+      <literal role="priv">SUPER</literal> privilege.
+    </para>
+
     <note>
       <para>
         <literal role="func">PASSWORD()</literal> encryption differs


Modified: trunk/refman-5.5/replication-notes.xml
===================================================================
--- trunk/refman-5.5/replication-notes.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.5/replication-notes.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 877 bytes

@@ -3583,6 +3583,14 @@
       </para>
 
       <para>
+        The <literal role="sysvar">read_only</literal> system variable
+        is not replicated. In addition, the enabling this variable has
+        different effects with regard to temporary tables, table
+        locking, and the <literal role="stmt">SET PASSWORD</literal>
+        statement in different MySQL versions.
+      </para>
+
+      <para>
         In statement-based replication, session variables are not
         replicated properly when used in statements that update tables.
         For example, the following sequence of statements will not


Modified: trunk/refman-5.5/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.5/sql-syntax-server-administration.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.5/sql-syntax-server-administration.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 856 bytes

@@ -1963,6 +1963,13 @@
       </para>
 
       <para>
+        In MySQL 5.1 and later, when the
+        <literal role="sysvar">read_only</literal> system variable is
+        enabled, the <literal role="priv">SUPER</literal> privilege is
+        required to use <literal role="stmt">SET PASSWORD</literal>.
+      </para>
+
+      <para>
         With a <literal>FOR</literal> clause, this statement sets the
         password for a specific account on the current server host. Only
         clients that have the <literal role="stmt">UPDATE</literal>


Modified: trunk/refman-5.6/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-5.6/dba-mysqld-server-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.6/dba-mysqld-server-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 18, Lines Deleted: 0; 1321 bytes

@@ -8733,6 +8733,24 @@
           master.
         </para>
 
+        <important>
+          <para>
+            In MySQL &current-series;, enabling
+            <literal>read_only</literal> prevents the use of the
+            <literal role="stmt">SET PASSWORD</literal> statement by any
+            user not having the <literal role="priv">SUPER</literal>
+            privilege. This is not necessarily the case for all MySQL
+            release series. When replicating from one MySQL release
+            series to another (for example, from a MySQL 5.0 master to a
+            MySQL 5.1 or later slave), you should check the
+            documentation for the versions running on both master and
+            slave to determine whether the behavior of
+            <literal>read_only</literal> in this regard is or is not the
+            same, and, if it is different, whether this has an impact on
+            your applications.
+          </para>
+        </important>
+
         <para>
           The following conditions apply:
         </para>


Modified: trunk/refman-5.6/dba-user-management-core.xml
===================================================================
--- trunk/refman-5.6/dba-user-management-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.6/dba-user-management-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 735 bytes

@@ -1268,6 +1268,14 @@
 
     </itemizedlist>
 
+    <para>
+      In MySQL &current-series;, enabling the
+      <literal role="sysvar">read_only</literal> system variable
+      prevents the use of the <literal role="stmt">SET
+      PASSWORD</literal> statement by any user not having the
+      <literal role="priv">SUPER</literal> privilege.
+    </para>
+
     <note>
       <para>
         <literal role="func">PASSWORD()</literal> encryption differs


Modified: trunk/refman-5.6/replication-notes.xml
===================================================================
--- trunk/refman-5.6/replication-notes.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.6/replication-notes.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 877 bytes

@@ -3558,6 +3558,14 @@
       </para>
 
       <para>
+        The <literal role="sysvar">read_only</literal> system variable
+        is not replicated. In addition, the enabling this variable has
+        different effects with regard to temporary tables, table
+        locking, and the <literal role="stmt">SET PASSWORD</literal>
+        statement in different MySQL versions.
+      </para>
+
+      <para>
         In statement-based replication, session variables are not
         replicated properly when used in statements that update tables.
         For example, the following sequence of statements will not


Modified: trunk/refman-5.6/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-5.6/sql-syntax-server-administration.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-5.6/sql-syntax-server-administration.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 856 bytes

@@ -1957,6 +1957,13 @@
       </para>
 
       <para>
+        In MySQL 5.1 and later, when the
+        <literal role="sysvar">read_only</literal> system variable is
+        enabled, the <literal role="priv">SUPER</literal> privilege is
+        required to use <literal role="stmt">SET PASSWORD</literal>.
+      </para>
+
+      <para>
         With a <literal>FOR</literal> clause, this statement sets the
         password for a specific account on the current server host. Only
         clients that have the <literal role="stmt">UPDATE</literal>


Modified: trunk/refman-6.0/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-6.0/dba-mysqld-server-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-6.0/dba-mysqld-server-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 18, Lines Deleted: 0; 1321 bytes

@@ -9340,6 +9340,24 @@
           master.
         </para>
 
+        <important>
+          <para>
+            In MySQL &current-series;, enabling
+            <literal>read_only</literal> prevents the use of the
+            <literal role="stmt">SET PASSWORD</literal> statement by any
+            user not having the <literal role="priv">SUPER</literal>
+            privilege. This is not necessarily the case for all MySQL
+            release series. When replicating from one MySQL release
+            series to another (for example, from a MySQL 5.0 master to a
+            MySQL 5.1 or later slave), you should check the
+            documentation for the versions running on both master and
+            slave to determine whether the behavior of
+            <literal>read_only</literal> in this regard is or is not the
+            same, and, if it is different, whether this has an impact on
+            your applications.
+          </para>
+        </important>
+
         <para>
           The following conditions apply:
         </para>


Modified: trunk/refman-6.0/dba-user-management-core.xml
===================================================================
--- trunk/refman-6.0/dba-user-management-core.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-6.0/dba-user-management-core.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 735 bytes

@@ -1255,6 +1255,14 @@
 
     </itemizedlist>
 
+    <para>
+      In MySQL &current-series;, enabling the
+      <literal role="sysvar">read_only</literal> system variable
+      prevents the use of the <literal role="stmt">SET
+      PASSWORD</literal> statement by any user not having the
+      <literal role="priv">SUPER</literal> privilege.
+    </para>
+
     <note>
       <para>
         <literal role="func">PASSWORD()</literal> encryption differs


Modified: trunk/refman-6.0/replication-notes.xml
===================================================================
--- trunk/refman-6.0/replication-notes.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-6.0/replication-notes.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 2; 1238 bytes

@@ -3216,11 +3216,20 @@
 
       <para>
         The <literal role="sysvar">storage_engine</literal> system
-        variable is not replicated, which is a good thing for
-        replication between different storage engines.
+        variable is not replicated, regardless of the logging mode; this
+        is intended to facilitate replication between different storage
+        engines.
       </para>
 
       <para>
+        The <literal role="sysvar">read_only</literal> system variable
+        is not replicated. In addition, the enabling this variable has
+        different effects with regard to temporary tables, table
+        locking, and the <literal role="stmt">SET PASSWORD</literal>
+        statement in different MySQL versions.
+      </para>
+
+      <para>
         In statement-based replication, session variables are not
         replicated properly when used in statements that update tables.
         For example, the following sequence of statements will not


Modified: trunk/refman-6.0/sql-syntax-server-administration.xml
===================================================================
--- trunk/refman-6.0/sql-syntax-server-administration.xml	2011-01-07 20:15:58 UTC (rev 24740)
+++ trunk/refman-6.0/sql-syntax-server-administration.xml	2011-01-07 23:46:22 UTC (rev 24741)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 856 bytes

@@ -1839,6 +1839,13 @@
       </para>
 
       <para>
+        In MySQL 5.1 and later, when the
+        <literal role="sysvar">read_only</literal> system variable is
+        enabled, the <literal role="priv">SUPER</literal> privilege is
+        required to use <literal role="stmt">SET PASSWORD</literal>.
+      </para>
+
+      <para>
         With a <literal>FOR</literal> clause, this statement sets the
         password for a specific account on the current server host. Only
         clients that have the <literal role="stmt">UPDATE</literal>


Thread
svn commit - mysqldoc@docsrva: r24741 - in trunk: refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0jon.stephens8 Jan