Attachment 68953 Details for Bug 106814 – Update to mysql-upgrading.xml

[patch] Update to mysql-upgrading.xml

mysql-upgrading.diff (text/plain), 3.31 KB, created by Michael Kohl (RETIRED) on 2005-09-21 11:41:48 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Michael Kohl (RETIRED)

Created: 2005-09-21 11:41:48 UTC

Size: 3.31 KB

patch

obsolete

>--- en/mysql-upgrading.xml	2005-09-21 20:22:56.000000000 +0200
>+++ mysql-upgrading.xml	2005-09-21 20:39:10.000000000 +0200
>@@ -50,8 +50,8 @@
> <body>
> 
> 
>-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:
> 
> 
> <pre caption="Dump of all databases">
>@@ -67,17 +67,18 @@
> --hex-blob \
> --master-data \
> --max_allowed_packet=16M \
>+ --quote-names
> --result-file=BACKUP_MYSQL_4.0.SQL
> </pre>
> 
> 
>-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.
> 
> 
> 
>-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.
> 
> 
> </body>
>@@ -90,7 +91,7 @@
> <body>
> 
> 
>-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:
> 
> 
>@@ -99,7 +100,7 @@
> </pre>
> 
> 
>-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:
> 
> 
> <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. 
>-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 twi 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>
> 
> 
>@@ -180,8 +180,7 @@
> <body>
> 
> 
>-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.
> 
> 
> <pre caption="Back to the past">
>@@ -189,7 +188,7 @@
> # emerge -C mysql
> # rm -rf /var/lib/mysql/ /var/log/mysql
> # emerge --usepkgonly "&lt;mysql-4.1"
>-# tar -xjpvf mysql.[tag] -C/tmp
>+# tar -xjpvf mysql.[tag] -C /
> # /etc/init.d/mysql start
> </pre>
> 
>@@ -203,10 +202,10 @@
> <body>
> 
> 
>-Under particular conditions it's possible to upgrade directly to the next major
>-version of MySQL. 
>-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.
> 
> 
> <pre caption="Straight upgrade">
>@@ -227,7 +226,7 @@
> </pre>
> 
> 
>-Good luck and don't ask.
>+Good luck and don't if something fails, don't say we didn't warn you! ;-)
> 
> 
> </body>

Actions: View | Diff

Attachments on bug 106814: 68953