bk commit - mysqldoc@docsrva tree (jon:1.2917)

[jon]

Below is the list of changes that have just been committed into a local
mysqldoc repository of jon. When jon does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2917 05/06/30 17:04:49 jon@stripped +2 -0
  Deleted section from installing.xml: downgrading-to-4-0.
  
  Updated deleted-sections file.

  refman-5.0/installing.xml
    1.4 05/06/30 17:04:47 jon@stripped +0 -54
    Deleted section: downgrading-to-4-0.

  refman-5.0/deleted-sections.txt
    1.6 05/06/30 17:04:47 jon@stripped +2 -0
    Added ID of deleted section downgrading-to-4-0

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	jon
# Host:	gigan.site
# Root:	/home/jon/bk/mysqldoc

--- 1.5/refman-5.0/deleted-sections.txt	2005-06-30 16:43:33 +10:00
+++ 1.6/refman-5.0/deleted-sections.txt	2005-06-30 17:04:47 +10:00
@@ -17,6 +17,8 @@
 upgrading-from-3-21
 upgrading-from-3-20
 
+downgrading-to-4-0
+
 # from news.xml:
 
 news-4-1-x

--- 1.3/refman-5.0/installing.xml	2005-06-30 12:37:33 +10:00
+++ 1.4/refman-5.0/installing.xml	2005-06-30 17:04:47 +10:00
@@ -11868,60 +11868,6 @@
 
   </section>
 
-  <section id="downgrading-to-4-0">
-
-   <title id='title-downgrading-to-4-0'>&title-downgrading-to-4-0;</title>
-
-   <para>
-    The table format in 4.1 changed to include more and new character
-    set information. Because of this, you must use
-    <command>mysqldump</command> to dump any tables you have created
-    with the newer MySQL server. For example, if all the tables in a
-    particular database need to be dumped to be reverted back to MySQL
-    4.0 format, use this command:
-   </para>
-
-<programlisting>
-shell&gt; mysqldump --create-options --compatible=mysql40 <replaceable>db_name</replaceable> &gt; <replaceable>dump_file</replaceable>
-</programlisting>
-
-   <para>
-    Then stop the newer server, restart the older server, and read in
-    the dump file:
-   </para>
-
-<programlisting>
-shell&gt; mysql <replaceable>db_name</replaceable> &lt; <replaceable>dump_file</replaceable>
-</programlisting>
-
-   <para>
-    In the special case that you're downgrading
-    <literal>MyISAM</literal> tables, no special treatment is necessary
-    if all columns in the tables contain only numeric columns or string
-    columns (<literal>CHAR</literal>, <literal>VARCHAR</literal>,
-    <literal>TEXT</literal>, and so forth) that contain only
-    <literal>latin1</literal> data. Your 4.1 tables should be directly
-    usable with a 4.0 server.
-   </para>
-
-   <para>
-    If you used the <literal>mysql_fix_privilege_tables</literal> script
-    to upgrade the grant tables, you can either use the preceding method
-    to convert them to back to MySQL 4.0 or do the following in MySQL
-    4.1 (or above):
-   </para>
-
-<programlisting>
-ALTER TABLE mysql.user CONVERT TO CHARACTER SET latin1 COLLATE latin1_swedish_ci;
-ALTER TABLE mysql.db CONVERT TO CHARACTER SET latin1 COLLATE latin1_swedish_ci;
-ALTER TABLE mysql.host CONVERT TO CHARACTER SET latin1 COLLATE latin1_swedish_ci;
-ALTER TABLE mysql.tables_priv CONVERT TO CHARACTER SET latin1 COLLATE latin1_swedish_ci;
-ALTER TABLE mysql.columns_priv CONVERT TO CHARACTER SET latin1 COLLATE latin1_swedish_ci;
-ALTER TABLE mysql.func CONVERT TO CHARACTER SET latin1 COLLATE latin1_swedish_ci;
-</programlisting>
-
-  </section>
-
  </section>
 
  <section id="operating-system-specific-notes">