Author: paul
Date: 2008-05-30 16:38:00 +0200 (Fri, 30 May 2008)
New Revision: 10865
Log:
r31763@frost: paul | 2008-05-30 09:38:12 -0500
Some additional information for BACKUP DATABASE, RESTORE.
Modified:
trunk/refman-6.0/dba-core.xml
trunk/refman-6.0/restrictions.xml
trunk/refman-6.0/sql-syntax.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:31761
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31512
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:31763
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:31512
Modified: trunk/refman-6.0/dba-core.xml
===================================================================
--- trunk/refman-6.0/dba-core.xml 2008-05-30 01:34:33 UTC (rev 10864)
+++ trunk/refman-6.0/dba-core.xml 2008-05-30 14:38:00 UTC (rev 10865)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 3; 910 bytes
@@ -6841,9 +6841,10 @@
By default, this variable is empty. If set to the name of a
directory, it limits the effect of the
<function role="sql">LOAD_FILE()</function> function and the
- <literal>LOAD DATA</literal> and <literal>SELECT ... INTO
- OUTFILE</literal> statements to work only with files in that
- directory.
+ <literal>LOAD DATA</literal>, <literal>SELECT ... INTO
+ OUTFILE</literal>, <literal>BACKUP DATABASE</literal>, and
+ <literal>RESTORE</literal> statements to work only with
+ files in that directory.
</para>
</listitem>
Modified: trunk/refman-6.0/restrictions.xml
===================================================================
--- trunk/refman-6.0/restrictions.xml 2008-05-30 01:34:33 UTC (rev 10864)
+++ trunk/refman-6.0/restrictions.xml 2008-05-30 14:38:00 UTC (rev 10865)
Changed blocks: 1, Lines Added: 8, Lines Deleted: 0; 549 bytes
@@ -1259,6 +1259,14 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ <literal>BACKUP DATABASE</literal> and
+ <literal>RESTORE</literal> cannot be used as prepared
+ statements.
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
Modified: trunk/refman-6.0/sql-syntax.xml
===================================================================
--- trunk/refman-6.0/sql-syntax.xml 2008-05-30 01:34:33 UTC (rev 10864)
+++ trunk/refman-6.0/sql-syntax.xml 2008-05-30 14:38:00 UTC (rev 10865)
Changed blocks: 4, Lines Added: 22, Lines Deleted: 4; 2430 bytes
@@ -15188,8 +15188,8 @@
However, although no implicit commit occurs, neither can the
statement be rolled back. Therefore, use of such statements
will violate transaction atomicity: For example, if you use
- <literal>CREATE TEMPORARY TABLE</literal> and then roll
- back the transaction, the table remains in existence.
+ <literal>CREATE TEMPORARY TABLE</literal> and then roll back
+ the transaction, the table remains in existence.
</para>
</listitem>
@@ -19434,9 +19434,19 @@
</programlisting>
<para>
+ While the operation is in progress, it can be monitored as
+ described in
+ <xref linkend="backup-database-restore-monitoring"/>.
+ </para>
+
+ <para>
<literal>BACKUP DATABASE</literal> backs up database and table
definitions, table data, stored routines, triggers, events,
- and views.
+ and views. <literal>TEMPORARY</literal> tables are not
+ included. For anything else not explicitly listed, assume that
+ it is ot backed up. This includes but is not limited to items
+ such as privileges, UDF definitions and files, logs, and
+ option files.
</para>
<para>
@@ -19445,7 +19455,9 @@
<literal>INFORMATION_SCHEMA</literal> databases. The statement
silently ignores them if you use the <literal>*</literal>
database selector syntax. Do not include them in the list of
- names if you specify database names explicitly.
+ names if you specify database names explicitly. To back up the
+ <literal>mysql</literal> database, you can use the
+ <command>mysqldump</command> program.
</para>
<remark role="help-description-end"/>
@@ -19532,6 +19544,12 @@
+-----------+
</programlisting>
+ <para>
+ While the operation is in progress, it can be monitored as
+ described in
+ <xref linkend="backup-database-restore-monitoring"/>.
+ </para>
+
<caution>
<para>
<literal>RESTORE</literal> is a destructive operation. Each
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10865 - in trunk: . refman-6.0 | paul | 30 May |
