MySQL Lists are EOL. Please join:

List:Commits« Previous MessageNext Message »
From:paul.dubois Date:April 21 2010 6:48pm
Subject:svn commit - mysqldoc@docsrva: r20181 - in trunk: . dynamic-docs/changelog mysql-backup refman-6.0
View as plain text  
Author: paul
Date: 2010-04-21 20:48:51 +0200 (Wed, 21 Apr 2010)
New Revision: 20181

Log:
 r58126@frost:  paul | 2010-04-21 13:45:58 -0500
 Fix auto-link markup


Modified:
   trunk/dynamic-docs/changelog/mysqld-1.xml
   trunk/dynamic-docs/changelog/mysqld-2.xml
   trunk/dynamic-docs/changelog/mysqld.xml
   trunk/mysql-backup/optvars.xml
   trunk/refman-6.0/dba-mysqld-server-core.xml
   trunk/refman-6.0/introduction.xml

Property changes on: trunk
___________________________________________________________________
Name: svk:merge
   - 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:38445
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:58125
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546
   + 07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/mysqldoc/trunk:35498
07c7e7b4-24e3-4b51-89d0-6dc09fec6bec:/mysqldoc-local/trunk:38445
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:43968
4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/trunk:44480
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:58126
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:39036
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/trunk:39546


Modified: trunk/dynamic-docs/changelog/mysqld-1.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-1.xml	2010-04-21 18:48:42 UTC (rev 20180)
+++ trunk/dynamic-docs/changelog/mysqld-1.xml	2010-04-21 18:48:51 UTC (rev 20181)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 6; 1310 bytes

@@ -58914,9 +58914,9 @@
     <message>
 
       <para>
-        The <literal role="sysvar">innodb_log_arch_dir</literal> system
-        variable is no longer available but was present in some of the
-        sample option files included with MySQL distributions (such as
+        The <literal>innodb_log_arch_dir</literal> system variable is no
+        longer available but was present in some of the sample option
+        files included with MySQL distributions (such as
         <filename>my-huge.cnf</filename>). The line was present as a
         comment but uncommenting it would cause server startup failure
         so the line has been removed.

@@ -71151,9 +71151,8 @@
     <message>
 
       <para>
-        The <literal role="sysvar">have_community_features</literal>
-        system variable was renamed to
-        <literal role="sysvar">have_profiling</literal>.
+        The <literal>have_community_features</literal> system variable
+        was renamed to <literal role="sysvar">have_profiling</literal>.
       </para>
 
       <para>


Modified: trunk/dynamic-docs/changelog/mysqld-2.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld-2.xml	2010-04-21 18:48:42 UTC (rev 20180)
+++ trunk/dynamic-docs/changelog/mysqld-2.xml	2010-04-21 18:48:51 UTC (rev 20181)
Changed blocks: 2, Lines Added: 12, Lines Deleted: 12; 2573 bytes

@@ -12097,17 +12097,17 @@
             <literal role="sysvar">backup_elevation</literal>: To use
             the <literal role="stmt">BACKUP DATABASE</literal>
             statement, a user must have the
-            <literal role="priv">BACKUP</literal> for each database to
-            be included in the backup image. Assuming that this is true,
-            the <literal role="sysvar">backup_elevation</literal>
-            variable determines whether privilege elevation occurs
-            internally. If this variable is enabled (the default),
-            privilege elevation occurs and enables the backup to succeed
-            even if the user does not have the privileges required to
-            access all objects in the backup image. If the variable is
-            disabled, privilege elevation does not occur and an error
-            occurs if the user does not have the privileges required to
-            access all objects.
+            <literal role="priv">BACKUP</literal> privilege for each
+            database to be included in the backup image. Assuming that
+            this is true, the
+            <literal role="sysvar">backup_elevation</literal> variable
+            determines whether privilege elevation occurs internally. If
+            this variable is enabled (the default), privilege elevation
+            occurs and enables the backup to succeed even if the user
+            does not have the privileges required to access all objects
+            in the backup image. If the variable is disabled, privilege
+            elevation does not occur and an error occurs if the user
+            does not have the privileges required to access all objects.
           </para>
         </listitem>
 

@@ -12127,7 +12127,7 @@
             occurs and enables the restore to succeed even if the user
             does not have the privileges required to access all objects
             in the backup image. If the variable is disabled or the user
-            does not have <literal role="stmt">SUPER</literal>,
+            does not have <literal role="priv">SUPER</literal>,
             privilege elevation does not occur and an error occurs if
             the user does not have the required privileges privileges.
             In the absence of privilege elevation, the restore either


Modified: trunk/dynamic-docs/changelog/mysqld.xml
===================================================================
--- trunk/dynamic-docs/changelog/mysqld.xml	2010-04-21 18:48:42 UTC (rev 20180)
+++ trunk/dynamic-docs/changelog/mysqld.xml	2010-04-21 18:48:51 UTC (rev 20181)
Changed blocks: 4, Lines Added: 10, Lines Deleted: 10; 2368 bytes

@@ -77336,8 +77336,8 @@
 
         <listitem>
           <para>
-            The <literal role="stmt">SHOW INNODB STATUS</literal> and
-            <literal>SHOW MUTEX STATUS</literal> SQL statements (use
+            The <literal>SHOW INNODB STATUS</literal> and <literal>SHOW
+            MUTEX STATUS</literal> SQL statements (use
             <literal role="stmt" condition="show-engine">SHOW ENGINE
             INNODB STATUS</literal>
             <literal role="stmt" condition="show-engine">SHOW ENGINE

@@ -77364,9 +77364,9 @@
 
         <listitem>
           <para>
-            The <literal role="stmt">BACKUP TABLE</literal> and
-            <literal role="stmt">RESTORE TABLE</literal> SQL statements
-            (use <command>mysqldump</command> or
+            The <literal>BACKUP TABLE</literal> and <literal>RESTORE
+            TABLE</literal> SQL statements (use
+            <command>mysqldump</command> or
             <command>mysqlhotcopy</command> to dump tables and
             <command>mysql</command> to reload dump files).
           </para>

@@ -77505,8 +77505,8 @@
 
         <listitem>
           <para>
-            The <literal role="stmt">SHOW INNODB STATUS</literal> and
-            <literal>SHOW MUTEX STATUS</literal> SQL statements (use
+            The <literal>SHOW INNODB STATUS</literal> and <literal>SHOW
+            MUTEX STATUS</literal> SQL statements (use
             <literal role="stmt" condition="show-engine">SHOW ENGINE
             INNODB STATUS</literal>
             <literal role="stmt" condition="show-engine">SHOW ENGINE

@@ -77533,9 +77533,9 @@
 
         <listitem>
           <para>
-            The <literal role="stmt">BACKUP TABLE</literal> and
-            <literal role="stmt">RESTORE TABLE</literal> SQL statements
-            (use <command>mysqldump</command> or
+            The <literal>BACKUP TABLE</literal> and <literal>RESTORE
+            TABLE</literal> SQL statements (use
+            <command>mysqldump</command> or
             <command>mysqlhotcopy</command> to dump tables and
             <command>mysql</command> to reload dump files).
           </para>


Modified: trunk/mysql-backup/optvars.xml
===================================================================
--- trunk/mysql-backup/optvars.xml	2010-04-21 18:48:42 UTC (rev 20180)
+++ trunk/mysql-backup/optvars.xml	2010-04-21 18:48:51 UTC (rev 20181)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 3; 1491 bytes

@@ -174,8 +174,9 @@
         <para>
           To use the <literal role="stmt">BACKUP DATABASE</literal>
           statement, a user must have the
-          <literal role="priv">BACKUP</literal> for each database to be
-          included in the backup image. Assuming that this is true, the
+          <literal role="priv">BACKUP</literal> privilege for each
+          database to be included in the backup image. Assuming that
+          this is true, the
           <literal role="sysvar">backup_elevation</literal> variable
           determines whether privilege elevation occurs internally. If
           this variable is enabled (the default), privilege elevation

@@ -443,7 +444,7 @@
           occurs and enables the restore to succeed even if the user
           does not have the privileges required to access all objects in
           the backup image. If the variable is disabled or the user does
-          not have <literal role="stmt">SUPER</literal>, privilege
+          not have <literal role="priv">SUPER</literal>, privilege
           elevation does not occur and an error occurs if the user does
           not have the required privileges privileges. In the absence of
           privilege elevation, the restore either performs privilege


Modified: trunk/refman-6.0/dba-mysqld-server-core.xml
===================================================================
--- trunk/refman-6.0/dba-mysqld-server-core.xml	2010-04-21 18:48:42 UTC (rev 20180)
+++ trunk/refman-6.0/dba-mysqld-server-core.xml	2010-04-21 18:48:51 UTC (rev 20181)
Changed blocks: 2, Lines Added: 152, Lines Deleted: 0; 6783 bytes

@@ -3904,6 +3904,43 @@
       </listitem>
 
       <listitem>
+        <para id="sysvar_backup_elevation">
+          <indexterm>
+            <primary>backup_elevation system variable</primary>
+          </indexterm>
+
+          <indexterm>
+            <primary>system variable</primary>
+            <secondary>backup_elevation</secondary>
+          </indexterm>
+
+          <literal role="sysvar">backup_elevation</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item" role="6.0:mysqld:backup_elevation"/>
+
+        <para>
+          To use the <literal role="stmt">BACKUP DATABASE</literal>
+          statement, a user must have the
+          <literal role="priv">BACKUP</literal> privilege for each
+          database to be included in the backup image. Assuming that
+          this is true, the
+          <literal role="sysvar">backup_elevation</literal> variable
+          determines whether privilege elevation occurs internally. If
+          this variable is enabled (the default), privilege elevation
+          occurs and enables the backup to succeed even if the user does
+          not have the privileges required to access all objects in the
+          backup image. If the variable is disabled, privilege elevation
+          does not occur and an error occurs if the user does not have
+          the privileges required to access all objects.
+        </para>
+
+        <para>
+          This variable was added in MySQL 6.0.14.
+        </para>
+      </listitem>
+
+      <listitem>
         <para id="sysvar_backup_history_log">
           <indexterm>
             <primary>backup_history_log system variable</primary>

@@ -8985,6 +9022,121 @@
       </listitem>
 
       <listitem>
+        <para id="sysvar_restore_disables_events">
+          <indexterm>
+            <primary>restore_disables_events system variable</primary>
+          </indexterm>
+
+          <indexterm>
+            <primary>system variable</primary>
+            <secondary>restore_disables_events</secondary>
+          </indexterm>
+
+          <literal role="sysvar">restore_disables_events</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item" role="6.0:mysqld:restore_disables_events"/>
+
+        <para>
+          If this variable is enabled (the default),
+          <literal role="stmt">RESTORE</literal> disables Event
+          Scheduler events that are restored from the backup image. If
+          the variable is disabled, restored events retain their state
+          as recorded in the image.
+        </para>
+
+        <para>
+          This variable was added in MySQL 6.0.14.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para id="sysvar_restore_elevation">
+          <indexterm>
+            <primary>restore_elevation system variable</primary>
+          </indexterm>
+
+          <indexterm>
+            <primary>system variable</primary>
+            <secondary>restore_elevation</secondary>
+          </indexterm>
+
+          <literal role="sysvar">restore_elevation</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item" role="6.0:mysqld:restore_elevation"/>
+
+        <para>
+          To use the <literal role="stmt">RESTORE</literal> statement, a
+          user must have the <literal role="priv">RESTORE</literal>
+          privilege for each database in the backup image. Assuming that
+          this is true, the
+          <literal role="sysvar">restore_elevation</literal> variable
+          determines, in conjunction with whether the user also has the
+          <literal role="priv">SUPER</literal> privilege, whether
+          privilege elevation occurs internally. If this variable is
+          enabled (the default) and the user has
+          <literal role="priv">SUPER</literal>, privilege elevation
+          occurs and enables the restore to succeed even if the user
+          does not have the privileges required to access all objects in
+          the backup image. If the variable is disabled or the user does
+          not have <literal role="priv">SUPER</literal>, privilege
+          elevation does not occur and an error occurs if the user does
+          not have the required privileges privileges. In the absence of
+          privilege elevation, the restore either performs privilege
+          prechecking before attempting to restore objects or checks
+          privileges for each object before restoring it. The
+          <literal role="sysvar">restore_precheck</literal> variable
+          determines whether prechecking occurs.
+        </para>
+
+        <para>
+          This variable was added in MySQL 6.0.14.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para id="sysvar_restore_precheck">
+          <indexterm>
+            <primary>restore_precheck system variable</primary>
+          </indexterm>
+
+          <indexterm>
+            <primary>system variable</primary>
+            <secondary>restore_precheck</secondary>
+          </indexterm>
+
+          <literal role="sysvar">restore_precheck</literal>
+        </para>
+
+        <para condition="dynamic:optvar:item" role="6.0:mysqld:restore_precheck"/>
+
+        <para>
+          This variable determines whether privilege prechecking is used
+          when the <literal role="stmt">RESTORE</literal> statement does
+          not use privilege elevation. (Elevation is not used if the
+          <literal role="sysvar">restore_elevation</literal> variable is
+          disabled or the user does not have the
+          <literal role="priv">SUPER</literal> privilege.) When
+          privilege elevation does not occur and
+          <literal role="sysvar">restore_precheck</literal> is enabled
+          (the default), the restore attempts to determine, before
+          restoring any objects from the backup image, whether the user
+          has all privileges required to access all the objects, and
+          fails with an error if not. If
+          <literal role="sysvar">restore_precheck</literal> is disabled,
+          prechecking does not occur and the restore performs privilege
+          checking for each object before restoring it. In this case,
+          the restore operation could fail in the middle due to errors
+          resulting from insufficient privileges.
+        </para>
+
+        <para>
+          This variable was added in MySQL 6.0.14.
+        </para>
+      </listitem>
+
+      <listitem>
         <para id="sysvar_rpl_semi_sync_master_enabled">
           <indexterm>
             <primary>rpl_semi_sync_master_enabled system variable</primary>


Modified: trunk/refman-6.0/introduction.xml
===================================================================
--- trunk/refman-6.0/introduction.xml	2010-04-21 18:48:42 UTC (rev 20180)
+++ trunk/refman-6.0/introduction.xml	2010-04-21 18:48:51 UTC (rev 20181)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 5; 1255 bytes

@@ -584,8 +584,8 @@
 
       <listitem>
         <para>
-          The <literal role="stmt">SHOW INNODB STATUS</literal> and
-          <literal>SHOW MUTEX STATUS</literal> SQL statements (use
+          The <literal>SHOW INNODB STATUS</literal> and <literal>SHOW
+          MUTEX STATUS</literal> SQL statements (use
           <literal role="stmt" condition="show-engine">SHOW ENGINE
           INNODB STATUS</literal>
           <literal role="stmt" condition="show-engine">SHOW ENGINE

@@ -612,9 +612,9 @@
 
       <listitem>
         <para>
-          The <literal role="stmt">BACKUP TABLE</literal> and
-          <literal role="stmt">RESTORE TABLE</literal> SQL statements
-          (use <command>mysqldump</command> or
+          The <literal>BACKUP TABLE</literal> and <literal>RESTORE
+          TABLE</literal> SQL statements (use
+          <command>mysqldump</command> or
           <command>mysqlhotcopy</command> to dump tables and
           <command>mysql</command> to reload dump files).
         </para>


Thread
svn commit - mysqldoc@docsrva: r20181 - in trunk: . dynamic-docs/changelog mysql-backup refman-6.0paul.dubois21 Apr