Author: paul
Date: 2008-04-24 20:43:59 +0200 (Thu, 24 Apr 2008)
New Revision: 10585
Log:
r30933@arctic: paul | 2008-04-24 13:43:35 -0500
Upgrade note revisions
Modified:
trunk/it/refman-5.1/installing-core.xml
trunk/pt/refman-5.1/installing-core.xml
trunk/refman-4.1/installing.xml
trunk/refman-5.0/installing-cs-core.xml
trunk/refman-5.1/installing-core.xml
trunk/refman-6.0/installing-core.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30938
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30930
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:35828
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:30938
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:30933
Modified: trunk/it/refman-5.1/installing-core.xml
===================================================================
--- trunk/it/refman-5.1/installing-core.xml 2008-04-24 18:22:07 UTC (rev 10584)
+++ trunk/it/refman-5.1/installing-core.xml 2008-04-24 18:43:59 UTC (rev 10585)
Changed blocks: 3, Lines Added: 32, Lines Deleted: 37; 4678 bytes
@@ -12212,16 +12212,18 @@
<para>
Read <emphasis>all</emphasis> the notes in
<xref linkend="upgrading-from-5-0"/>. These notes will enable
- you to identify any upgrade issues that apply to your current
- MySQL installation. Read <xref linkend="news"/> as well. These
- notes provide information about features that are new in MySQL
+ you to identify upgrade issues that apply to your current
+ MySQL installation. Read <xref linkend="news"/> as well, which
+ provides information about features that are new in MySQL
¤t-series; or differ from those found in MySQL
&previous-series;.
</para>
+ </listitem>
+ <listitem>
<para>
For any incompatibilities that require your attention
- <literal>before</literal> upgrading, deal with them as
+ <emphasis>before</emphasis> upgrading, deal with them as
described in <xref linkend="upgrading-from-5-0"/>.
</para>
</listitem>
@@ -12417,12 +12419,19 @@
</listitem>
</itemizedlist>
+ </listitem>
+ <listitem>
<para>
Note particularly any changes that are marked
<emphasis role="bold">Known issue</emphasis> or
- <emphasis role="bold">Incompatible change</emphasis>. Our
- aim is to avoid these changes, but occasionally they are
+ <emphasis role="bold">Incompatible change</emphasis>. These
+ incompatibilities with earlier versions of MySQL may require
+ your attention <emphasis>before you upgrade</emphasis>.
+ </para>
+
+ <para>
+ Our aim is to avoid these changes, but occasionally they are
necessary to correct problems that would be worse than an
incompatibility between releases. If any upgrade issue
applicable to your installation involves an incompatibility
@@ -12434,52 +12443,38 @@
</para>
<para>
- These incompatibilities with earlier versions of MySQL may
- require your attention <emphasis>before you
- upgrade</emphasis>. For example:
+ A dump and reload is done like this:
</para>
<itemizedlist>
<listitem>
<para>
- A dump and reload is done like this:
+ Dump the affected tables with
+ <command>mysqldump</command> <emphasis>before</emphasis>
+ upgrading
</para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Dump the affected tables with
- <command>mysqldump</command>
- <emphasis>before</emphasis> upgrading
- </para>
- </listitem>
-
- <listitem>
- <para>
- Reload the dump file (for example, with
- <command>mysql</command>) to recreate the tables
- after upgrading
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
<para>
- Any procedure that involves <literal>REPAIR
- TABLE</literal> with the <literal>USE_FRM</literal>
- option <emphasis>must</emphasis> be done before
- upgrading. Use of this statement with a version of MySQL
- different from the one used to create the table (that
- is, using it after upgrading) may damage the table. See
- <xref linkend="repair-table"/>.
+ Reload the dump file (for example, with
+ <command>mysql</command>) to recreate the tables after
+ upgrading
</para>
</listitem>
</itemizedlist>
+
+ <para>
+ Any procedure that involves <literal>REPAIR TABLE</literal>
+ with the <literal>USE_FRM</literal> option
+ <emphasis>must</emphasis> be done before upgrading. Use of
+ this statement with a version of MySQL different from the
+ one used to create the table (that is, using it after
+ upgrading) may damage the table. See
+ <xref linkend="repair-table"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/pt/refman-5.1/installing-core.xml
===================================================================
--- trunk/pt/refman-5.1/installing-core.xml 2008-04-24 18:22:07 UTC (rev 10584)
+++ trunk/pt/refman-5.1/installing-core.xml 2008-04-24 18:43:59 UTC (rev 10585)
Changed blocks: 3, Lines Added: 32, Lines Deleted: 37; 4678 bytes
@@ -12212,16 +12212,18 @@
<para>
Read <emphasis>all</emphasis> the notes in
<xref linkend="upgrading-from-5-0"/>. These notes will enable
- you to identify any upgrade issues that apply to your current
- MySQL installation. Read <xref linkend="news"/> as well. These
- notes provide information about features that are new in MySQL
+ you to identify upgrade issues that apply to your current
+ MySQL installation. Read <xref linkend="news"/> as well, which
+ provides information about features that are new in MySQL
¤t-series; or differ from those found in MySQL
&previous-series;.
</para>
+ </listitem>
+ <listitem>
<para>
For any incompatibilities that require your attention
- <literal>before</literal> upgrading, deal with them as
+ <emphasis>before</emphasis> upgrading, deal with them as
described in <xref linkend="upgrading-from-5-0"/>.
</para>
</listitem>
@@ -12417,12 +12419,19 @@
</listitem>
</itemizedlist>
+ </listitem>
+ <listitem>
<para>
Note particularly any changes that are marked
<emphasis role="bold">Known issue</emphasis> or
- <emphasis role="bold">Incompatible change</emphasis>. Our
- aim is to avoid these changes, but occasionally they are
+ <emphasis role="bold">Incompatible change</emphasis>. These
+ incompatibilities with earlier versions of MySQL may require
+ your attention <emphasis>before you upgrade</emphasis>.
+ </para>
+
+ <para>
+ Our aim is to avoid these changes, but occasionally they are
necessary to correct problems that would be worse than an
incompatibility between releases. If any upgrade issue
applicable to your installation involves an incompatibility
@@ -12434,52 +12443,38 @@
</para>
<para>
- These incompatibilities with earlier versions of MySQL may
- require your attention <emphasis>before you
- upgrade</emphasis>. For example:
+ A dump and reload is done like this:
</para>
<itemizedlist>
<listitem>
<para>
- A dump and reload is done like this:
+ Dump the affected tables with
+ <command>mysqldump</command> <emphasis>before</emphasis>
+ upgrading
</para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Dump the affected tables with
- <command>mysqldump</command>
- <emphasis>before</emphasis> upgrading
- </para>
- </listitem>
-
- <listitem>
- <para>
- Reload the dump file (for example, with
- <command>mysql</command>) to recreate the tables
- after upgrading
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
<para>
- Any procedure that involves <literal>REPAIR
- TABLE</literal> with the <literal>USE_FRM</literal>
- option <emphasis>must</emphasis> be done before
- upgrading. Use of this statement with a version of MySQL
- different from the one used to create the table (that
- is, using it after upgrading) may damage the table. See
- <xref linkend="repair-table"/>.
+ Reload the dump file (for example, with
+ <command>mysql</command>) to recreate the tables after
+ upgrading
</para>
</listitem>
</itemizedlist>
+
+ <para>
+ Any procedure that involves <literal>REPAIR TABLE</literal>
+ with the <literal>USE_FRM</literal> option
+ <emphasis>must</emphasis> be done before upgrading. Use of
+ this statement with a version of MySQL different from the
+ one used to create the table (that is, using it after
+ upgrading) may damage the table. See
+ <xref linkend="repair-table"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2008-04-24 18:22:07 UTC (rev 10584)
+++ trunk/refman-4.1/installing.xml 2008-04-24 18:43:59 UTC (rev 10585)
Changed blocks: 1, Lines Added: 4, Lines Deleted: 4; 806 bytes
@@ -12368,10 +12368,10 @@
<listitem>
<para>
- Read all the notes the upgrading section for the release
- series to which you are upgrading. Read the change notes as
- well. These provide information about new features you can
- use.
+ Read <emphasis>all</emphasis> the notes the upgrading section
+ for the release series to which you are upgrading. Read the
+ change notes as well. These provide information about new
+ features you can use.
</para>
</listitem>
Modified: trunk/refman-5.0/installing-cs-core.xml
===================================================================
--- trunk/refman-5.0/installing-cs-core.xml 2008-04-24 18:22:07 UTC (rev 10584)
+++ trunk/refman-5.0/installing-cs-core.xml 2008-04-24 18:43:59 UTC (rev 10585)
Changed blocks: 3, Lines Added: 32, Lines Deleted: 37; 4678 bytes
@@ -12917,16 +12917,18 @@
<para>
Read <emphasis>all</emphasis> the notes in
<xref linkend="upgrading-from-4-1"/>. These notes will enable
- you to identify any upgrade issues that apply to your current
- MySQL installation. Read <xref linkend="news"/> as well. These
- notes provide information about features that are new in MySQL
+ you to identify upgrade issues that apply to your current
+ MySQL installation. Read <xref linkend="news"/> as well, which
+ provides information about features that are new in MySQL
¤t-series; or differ from those found in MySQL
&previous-series;.
</para>
+ </listitem>
+ <listitem>
<para>
For any incompatibilities that require your attention
- <literal>before</literal> upgrading, deal with them as
+ <emphasis>before</emphasis> upgrading, deal with them as
described in <xref linkend="upgrading-from-4-1"/>.
</para>
</listitem>
@@ -13127,12 +13129,19 @@
</listitem>
</itemizedlist>
+ </listitem>
+ <listitem>
<para>
Note particularly any changes that are marked
<emphasis role="bold">Known issue</emphasis> or
- <emphasis role="bold">Incompatible change</emphasis>. Our
- aim is to avoid these changes, but occasionally they are
+ <emphasis role="bold">Incompatible change</emphasis>. These
+ incompatibilities with earlier versions of MySQL may require
+ your attention <emphasis>before you upgrade</emphasis>.
+ </para>
+
+ <para>
+ Our aim is to avoid these changes, but occasionally they are
necessary to correct problems that would be worse than an
incompatibility between releases. If any upgrade issue
applicable to your installation involves an incompatibility
@@ -13144,52 +13153,38 @@
</para>
<para>
- These incompatibilities with earlier versions of MySQL may
- require your attention <emphasis>before you
- upgrade</emphasis>. For example:
+ A dump and reload is done like this:
</para>
<itemizedlist>
<listitem>
<para>
- A dump and reload is done like this:
+ Dump the affected tables with
+ <command>mysqldump</command> <emphasis>before</emphasis>
+ upgrading
</para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Dump the affected tables with
- <command>mysqldump</command>
- <emphasis>before</emphasis> upgrading
- </para>
- </listitem>
-
- <listitem>
- <para>
- Reload the dump file (for example, with
- <command>mysql</command>) to recreate the tables
- after upgrading
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
<para>
- Any procedure that involves <literal>REPAIR
- TABLE</literal> with the <literal>USE_FRM</literal>
- option <emphasis>must</emphasis> be done before
- upgrading. Use of this statement with a version of MySQL
- different from the one used to create the table (that
- is, using it after upgrading) may damage the table. See
- <xref linkend="repair-table"/>.
+ Reload the dump file (for example, with
+ <command>mysql</command>) to recreate the tables after
+ upgrading
</para>
</listitem>
</itemizedlist>
+
+ <para>
+ Any procedure that involves <literal>REPAIR TABLE</literal>
+ with the <literal>USE_FRM</literal> option
+ <emphasis>must</emphasis> be done before upgrading. Use of
+ this statement with a version of MySQL different from the
+ one used to create the table (that is, using it after
+ upgrading) may damage the table. See
+ <xref linkend="repair-table"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/installing-core.xml
===================================================================
--- trunk/refman-5.1/installing-core.xml 2008-04-24 18:22:07 UTC (rev 10584)
+++ trunk/refman-5.1/installing-core.xml 2008-04-24 18:43:59 UTC (rev 10585)
Changed blocks: 3, Lines Added: 32, Lines Deleted: 37; 4669 bytes
@@ -12212,16 +12212,18 @@
<para>
Read <emphasis>all</emphasis> the notes in
<xref linkend="upgrading-from-5-0"/>. These notes will enable
- you to identify any upgrade issues that apply to your current
- MySQL installation. Read <xref linkend="news"/> as well. These
- notes provide information about features that are new in MySQL
+ you to identify upgrade issues that apply to your current
+ MySQL installation. Read <xref linkend="news"/> as well, which
+ provides information about features that are new in MySQL
¤t-series; or differ from those found in MySQL
&previous-series;.
</para>
+ </listitem>
+ <listitem>
<para>
For any incompatibilities that require your attention
- <literal>before</literal> upgrading, deal with them as
+ <emphasis>before</emphasis> upgrading, deal with them as
described in <xref linkend="upgrading-from-5-0"/>.
</para>
</listitem>
@@ -12417,12 +12419,19 @@
</listitem>
</itemizedlist>
+ </listitem>
+ <listitem>
<para>
Note particularly any changes that are marked
<emphasis role="bold">Known issue</emphasis> or
- <emphasis role="bold">Incompatible change</emphasis>. Our
- aim is to avoid these changes, but occasionally they are
+ <emphasis role="bold">Incompatible change</emphasis>. These
+ incompatibilities with earlier versions of MySQL may require
+ your attention <emphasis>before you upgrade</emphasis>.
+ </para>
+
+ <para>
+ Our aim is to avoid these changes, but occasionally they are
necessary to correct problems that would be worse than an
incompatibility between releases. If any upgrade issue
applicable to your installation involves an incompatibility
@@ -12434,52 +12443,38 @@
</para>
<para>
- These incompatibilities with earlier versions of MySQL may
- require your attention <emphasis>before you
- upgrade</emphasis>. For example:
+ A dump and reload is done like this:
</para>
<itemizedlist>
<listitem>
<para>
- A dump and reload is done like this:
+ Dump the affected tables with
+ <command>mysqldump</command> <emphasis>before</emphasis>
+ upgrading
</para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Dump the affected tables with
- <command>mysqldump</command>
- <emphasis>before</emphasis> upgrading
- </para>
- </listitem>
-
- <listitem>
- <para>
- Reload the dump file (for example, with
- <command>mysql</command>) to recreate the tables
- after upgrading
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
<para>
- Any procedure that involves <literal>REPAIR
- TABLE</literal> with the <literal>USE_FRM</literal>
- option <emphasis>must</emphasis> be done before
- upgrading. Use of this statement with a version of MySQL
- different from the one used to create the table (that
- is, using it after upgrading) may damage the table. See
- <xref linkend="repair-table"/>.
+ Reload the dump file (for example, with
+ <command>mysql</command>) to recreate the tables after
+ upgrading
</para>
</listitem>
</itemizedlist>
+
+ <para>
+ Any procedure that involves <literal>REPAIR TABLE</literal>
+ with the <literal>USE_FRM</literal> option
+ <emphasis>must</emphasis> be done before upgrading. Use of
+ this statement with a version of MySQL different from the
+ one used to create the table (that is, using it after
+ upgrading) may damage the table. See
+ <xref linkend="repair-table"/>.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-6.0/installing-core.xml
===================================================================
--- trunk/refman-6.0/installing-core.xml 2008-04-24 18:22:07 UTC (rev 10584)
+++ trunk/refman-6.0/installing-core.xml 2008-04-24 18:43:59 UTC (rev 10585)
Changed blocks: 3, Lines Added: 32, Lines Deleted: 37; 4669 bytes
@@ -12240,16 +12240,18 @@
<para>
Read <emphasis>all</emphasis> the notes in
<xref linkend="upgrading-from-5-1"/>. These notes will enable
- you to identify any upgrade issues that apply to your current
- MySQL installation. Read <xref linkend="news"/> as well. These
- notes provide information about features that are new in MySQL
+ you to identify upgrade issues that apply to your current
+ MySQL installation. Read <xref linkend="news"/> as well, which
+ provides information about features that are new in MySQL
¤t-series; or differ from those found in MySQL
&previous-series;.
</para>
+ </listitem>
+ <listitem>
<para>
For any incompatibilities that require your attention
- <literal>before</literal> upgrading, deal with them as
+ <emphasis>before</emphasis> upgrading, deal with them as
described in <xref linkend="upgrading-from-5-1"/>.
</para>
</listitem>
@@ -12427,12 +12429,19 @@
</listitem>
</itemizedlist>
+ </listitem>
+ <listitem>
<para>
Note particularly any changes that are marked
<emphasis role="bold">Known issue</emphasis> or
- <emphasis role="bold">Incompatible change</emphasis>. Our
- aim is to avoid these changes, but occasionally they are
+ <emphasis role="bold">Incompatible change</emphasis>. These
+ incompatibilities with earlier versions of MySQL may require
+ your attention <emphasis>before you upgrade</emphasis>.
+ </para>
+
+ <para>
+ Our aim is to avoid these changes, but occasionally they are
necessary to correct problems that would be worse than an
incompatibility between releases. If any upgrade issue
applicable to your installation involves an incompatibility
@@ -12444,52 +12453,38 @@
</para>
<para>
- These incompatibilities with earlier versions of MySQL may
- require your attention <emphasis>before you
- upgrade</emphasis>. For example:
+ A dump and reload is done like this:
</para>
<itemizedlist>
<listitem>
<para>
- A dump and reload is done like this:
+ Dump the affected tables with
+ <command>mysqldump</command> <emphasis>before</emphasis>
+ upgrading
</para>
-
- <itemizedlist>
-
- <listitem>
- <para>
- Dump the affected tables with
- <command>mysqldump</command>
- <emphasis>before</emphasis> upgrading
- </para>
- </listitem>
-
- <listitem>
- <para>
- Reload the dump file (for example, with
- <command>mysql</command>) to recreate the tables
- after upgrading
- </para>
- </listitem>
-
- </itemizedlist>
</listitem>
<listitem>
<para>
- Any procedure that involves <literal>REPAIR
- TABLE</literal> with the <literal>USE_FRM</literal>
- option <emphasis>must</emphasis> be done before
- upgrading. Use of this statement with a version of MySQL
- different from the one used to create the table (that
- is, using it after upgrading) may damage the table. See
- <xref linkend="repair-table"/>.
+ Reload the dump file (for example, with
+ <command>mysql</command>) to recreate the tables after
+ upgrading
</para>
</listitem>
</itemizedlist>
+
+ <para>
+ Any procedure that involves <literal>REPAIR TABLE</literal>
+ with the <literal>USE_FRM</literal> option
+ <emphasis>must</emphasis> be done before upgrading. Use of
+ this statement with a version of MySQL different from the
+ one used to create the table (that is, using it after
+ upgrading) may damage the table. See
+ <xref linkend="repair-table"/>.
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10585 - in trunk: . it/refman-5.1 pt/refman-5.1 refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 24 Apr |
