Gentoo Archives: gentoo-doc-cvs

From: Josh Saddler <nightmorph@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: mysql-upgrading.xml
Date: Fri, 29 Dec 2006 05:49:59
Message-Id: 20061229054948.68211646EB@smtp.gentoo.org
1 nightmorph 06/12/29 05:49:47
2
3 Modified: mysql-upgrading.xml
4 Log:
5 added MERGE tables note for bug 159340
6
7 Revision Changes Path
8 1.18 xml/htdocs/doc/en/mysql-upgrading.xml
9
10 file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.18&view=markup
11 plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.18&content-type=text/plain
12 diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?r1=1.17&r2=1.18
13
14 Index: mysql-upgrading.xml
15 ===================================================================
16 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v
17 retrieving revision 1.17
18 retrieving revision 1.18
19 diff -u -r1.17 -r1.18
20 --- mysql-upgrading.xml 4 Dec 2006 16:42:50 -0000 1.17
21 +++ mysql-upgrading.xml 29 Dec 2006 05:49:47 -0000 1.18
22 @@ -1,6 +1,6 @@
23 <?xml version='1.0' encoding="UTF-8"?>
24 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
25 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v 1.17 2006/12/04 16:42:50 nightmorph Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v 1.18 2006/12/29 05:49:47 nightmorph Exp $ -->
27
28 <guide link="/doc/en/mysql-upgrading.xml">
29 <title>Upgrade guide to MySQL 4.* or 5.0.*</title>
30 @@ -22,8 +22,8 @@
31 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
32 <license/>
33
34 -<version>1.14</version>
35 -<date>2006-12-04</date>
36 +<version>1.15</version>
37 +<date>2006-12-28</date>
38
39 <chapter>
40 <title>Straight upgrade, suggested for 4.1 =&gt; 5.0 migration</title>
41 @@ -35,6 +35,14 @@
42 direct upgrade to the next major version of MySQL.
43 </p>
44
45 +<note>
46 +This is not true for MERGE tables. You will likely run into trouble if you
47 +attempt a direct upgrade for this (rarely used) type of table. You should dump
48 +and recreate those tables and restore their contents in the process of
49 +upgrading. If unsure, you should begin with <uri link="#doc_chap2">Upgrading
50 +from old versions of MySQL</uri>.
51 +</note>
52 +
53 <pre caption="Straight upgrade from 4.1 to 5.0.*">
54 # <i>quickpkg dev-db/mysql</i>
55 # <i>alias MYSQL="mysql --user=root --password=</i><comment>'your_password'</comment><i>"</i>
56
57
58
59 --
60 gentoo-doc-cvs@g.o mailing list