From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GMWaB-0003QE-LO for garchives@archives.gentoo.org; Sun, 10 Sep 2006 21:11:16 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8ALBPuC003434; Sun, 10 Sep 2006 21:11:26 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8ALBOJw028197 for ; Sun, 10 Sep 2006 21:11:25 GMT Received: from lark (lark.gentoo.osuosl.org [140.211.166.177]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with SMTP id E81886466A for ; Sun, 10 Sep 2006 21:11:23 +0000 (UTC) Received: by lark (sSMTP sendmail emulation); Sun, 10 Sep 2006 21:11:22 +0000 From: "Josh Saddler" Date: Sun, 10 Sep 2006 21:11:22 +0000 To: gentoo-doc-cvs@lists.gentoo.org Subject: [gentoo-doc-cvs] cvs commit: mysql-upgrading.xml Message-Id: <20060910211123.E81886466A@smtp.gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-doc-cvs@gentoo.org Reply-to: docs-team@lists.gentoo.org X-Archives-Salt: fe7b1eb2-8e29-4cd0-8874-c2c8f4b6f03e X-Archives-Hash: 5009642273e2978de08762a1b59ee5c7 nightmorph 06/09/10 21:11:22 Modified: mysql-upgrading.xml Log: numerous fixes for bug 147078 Revision Changes Path 1.14 xml/htdocs/doc/en/mysql-upgrading.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.14&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.14&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml?r1=1.13&r2=1.14 Index: mysql-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- mysql-upgrading.xml 10 Sep 2006 01:57:15 -0000 1.13 +++ mysql-upgrading.xml 10 Sep 2006 21:11:22 -0000 1.14 @@ -1,6 +1,6 @@ - + Upgrade guide to MySQL 4.* or 5.0.* @@ -14,16 +14,16 @@ The MySQL herd is proud to announce that MySQL 5.0 will soon be found in -Gentoo's stable tree. This document describes how to upgrade from MySQL 4.* to -5.0.* +Gentoo's stable tree. This document describes how to upgrade to MySQL 4.* and +to 5.0.*. -1.10 -2006-09-09 +1.11 +2006-09-10 Straight upgrade, suggested for 4.1 => 5.0 migration @@ -31,11 +31,11 @@

-The myisam storage engine in 4.1 version was already mature enough to allow a +The myisam storage engine in version 4.1 was already mature enough to allow a direct upgrade to the next major version of MySQL.

-
+
 # quickpkg dev-db/mysql
 # alias MYSQL="mysql --user=root --password='your_password'"
 # DATADIR=$(MYSQL --batch --raw --silent --skip-column-names \
@@ -149,11 +149,11 @@
 
 Now two different backups should exist: the SQL one, which is portable between
 various versions of MySQL, and the other one that will allow you to quickly
-restore your database. This is covered later in this doc in more detail.
+restore your database. This is covered later in this document in more detail.
 
 
 

-After you got rid of your old MySQL installation, you can now install the new
+After you get rid of your old MySQL installation, you can now install the new
 version. Note that revdep-rebuild is necessary for rebuilding packages
 linking against MySQL.
 

@@ -187,16 +187,16 @@
 
 
 
-The default character set in gentoo mysql 4.1 and above is utf8. If the
-data contain non-ASCII characters, you may want to preserve the default
+The default character set in MySQL 4.1 and above is utf8. If the data
+contain non-ASCII characters, you may want to preserve the default
 character set of the database replacing all occurrences of utf8 with
-latin1 into the /etc/mysql/my.cnf config file. More
+latin1 in the /etc/mysql/my.cnf config file. More
 information can be found Charset
-conversion charapter.
+conversion chapter.
 
 
 
-The administrative mysql database that containins user names, passwords
+The administrative mysql database that contains user names, passwords
 amongst other things is and must be in encoded in utf8.
 
 
@@ -268,7 +268,7 @@
 
 
 

-This charapter is not intended to be an exhaustive guide on how to do such
+This chapter is not intended to be an exhaustive guide on how to do such
 conversions, rather a short list of hints on which the reader can elaborate.
 

 
@@ -285,8 +285,8 @@
 
 
 

-Every utf-8 char is considered 3 bytes long within an index. Indexes in MySQL
-can be up to 1000 bytes long (767 bytes for InnoDB tables). Note that the
+Every utf-8 character is considered 3 bytes long within an index. Indexes in
+MySQL can be up to 1000 bytes long (767 bytes for InnoDB tables). Note that the
 limits are measured in bytes, whereas the length of a column is interpreted as
 number of characters.
 

@@ -353,7 +353,7 @@
 Working in a utf-8 environment, with utf-8 editors and tools help too:
 

 
-
+
 LC_ALL=en_US.UTF-8
 LANG=en_US.UTF-8
 export LC_ALL LANG
@@ -409,7 +409,7 @@
 
 
 

-To use utf-8 with apache, you need to adjust the folowing variables in
+To use utf-8 with apache, you need to adjust the following variables in
 httpd.conf: AddDefaultCharset, CharsetDefault, CharsetSourceEnc.
 If your source html files aren't encoded in utf-8, they must be
 converted with iconv or recode.



-- 
gentoo-doc-cvs@gentoo.org mailing list