rane 05/09/21 19:15:49 Modified: xml/htdocs/doc/en mysql-upgrading.xml Log: update from #106814
Revision Changes Path 1.2 +21 -22 xml/htdocs/doc/en/mysql-upgrading.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.2&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrading.xml?rev=1.2&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/mysql-upgrading.xml.diff?r1=1.1&r2=1.2&cvsroot=gentoo Index: mysql-upgrading.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- mysql-upgrading.xml 11 Sep 2005 20:41:05 -0000 1.1 +++ mysql-upgrading.xml 21 Sep 2005 19:15:49 -0000 1.2 @@ -1,6 +1,6 @@ <?xml version='1.0' encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v 1.1 2005/09/11 20:41:05 rane Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/mysql-upgrading.xml,v 1.2 2005/09/21 19:15:49 rane Exp $ --> <guide link="/doc/en/mysql-upgrading.xml"> <title>Upgrade guide to MySQL 4.1.x</title> @@ -22,8 +22,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>1.0</version> -<date>2005-09-11</date> +<version>1.1</version> +<date>2005-09-21</date> <chapter> <title>Upgrading from old versions of MySQL</title> @@ -50,8 +50,8 @@ <body> <p> -One of the fundamental works of every database administrator is ... to make -backup of the data. So proceed with one. +One of the most important tasks that every database administrator has to perfom +is backing up data. Here we go: </p> <pre caption="Dump of all databases"> @@ -67,17 +67,18 @@ <i>--hex-blob \</i> <i>--master-data \</i> <i>--max_allowed_packet=16M \</i> + <i>--quote-names</i> <i>--result-file=BACKUP_MYSQL_4.0.SQL</i> </pre> <p> -Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, this one can be -used to recreate your data, the data is described in the MySQL dialect of SQL, +Now a file named <path>BACKUP_MYSQL_4.0.SQL</path> should exist, which later can +be used to recreate your data. The data is described in the MySQL dialect of SQL, the Structured Query Language. </p> <p> -This would be a good time to see if the backup you have created is working. +Now would also be a good time to see if the backup you have created is working. </p> </body> @@ -90,7 +91,7 @@ <body> <p> -If you have skipped step #1, you now have to create a backup package (the +If you have skipped step #1, you now have to create a backup package (of the database server, not the data) of the currently installed version: </p> @@ -99,7 +100,7 @@ </pre> <p> -Now it's time to clean out the current version and all it's data: +Now it's time to clean out the current version and all of its data: </p> <pre caption="Uninstall MySQL"> @@ -111,10 +112,9 @@ </pre> <note> -At this time two backup should exist, one portable between various MySQL -versions, the SQL one. <br /> -The other instead permit to restore quickly the system at this point. Later on -this doc will be explain how to recover from this last one. +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 will be covered later in this doc in more detail. </note> <p> @@ -180,8 +180,7 @@ <body> <p> -If the result is not fully satisfactory, it's possible to reinstall the old -MySQL 4.0 version. +If you are not happy with MySQL 4.1, it's possible to go back to MySQL 4.0. </p> <pre caption="Back to the past"> @@ -189,7 +188,7 @@ # <i>emerge -C mysql</i> # <i>rm -rf /var/lib/mysql/ /var/log/mysql</i> # <i>emerge --usepkgonly "<mysql-4.1"</i> -# <i>tar -xjpvf mysql.[tag] -C/tmp</i> +# <i>tar -xjpvf mysql.[tag] -C /</i> # <i>/etc/init.d/mysql start</i> </pre> @@ -203,10 +202,10 @@ <body> <p> -Under particular conditions it's possible to upgrade directly to the next major -version of MySQL.<br /> -If you know that this is your case, with a little trick it's possible to upgrade -straight to MySQL 4.1. +Under certain conditions it's possible to directly upgrade to the next major +version of MySQL. If you know what you're doing and think that applies to your +case, here's a little trick that makes it possible to directly upgrade to +MySQl 4.1. </p> <pre caption="Straight upgrade"> @@ -227,7 +226,7 @@ </pre> <p> -Good luck and don't ask. +Good luck and if something fails, don't say we didn't warn you! ;-) </p> </body> -- [email protected] mailing list
