List:Commits« Previous MessageNext Message »
From:john.russell Date:April 7 2011 7:22pm
Subject:svn commit - mysqldoc@oter02: r25788 - trunk/refman-5.6
View as plain text  
Author: jdrussel
Date: 2011-04-07 21:22:21 +0200 (Thu, 07 Apr 2011)
New Revision: 25788

Log:
Make language and links more generic when discussing the transition from
old to new InnoDB. Presumably still needed for people who might upgrade
MySQL 5.[01] -> MySQL 5.6, so shouldn't talk about 5.5 specifically.


Modified:
   trunk/refman-5.6/se-innodb-core.xml


Modified: trunk/refman-5.6/se-innodb-core.xml
===================================================================
--- trunk/refman-5.6/se-innodb-core.xml	2011-04-07 19:14:06 UTC (rev 25787)
+++ trunk/refman-5.6/se-innodb-core.xml	2011-04-07 19:22:21 UTC (rev 25788)
Changed blocks: 6, Lines Added: 24, Lines Deleted: 23; 3956 bytes

@@ -512,14 +512,15 @@
       </itemizedlist>
 
       <bridgehead>
-        Recent Improvements for InnoDB Tables (from the Plugin Era)
+        Recent Improvements for InnoDB Tables
       </bridgehead>
 
       <para>
-        If you have experience with InnoDB, but not the recent
-        incarnation known as the InnoDB Plugin, read about the latest
-        enhancements in <xref linkend="innodb-5-5"/>. To make a long
-        story short:
+        If you have experience with InnoDB, but from MySQL 5.1 or
+        earlier, read about the latest InnoDB enhancements in
+        <xref linkend="innodb-performance"/> and
+        <xref linkend="innodb-other-changes"/>. To make a long story
+        short:
       </para>
 
       <itemizedlist>

@@ -549,7 +550,8 @@
         <listitem>
           <para>
             The storage layout for table data is more efficient for
-            BLOBs and long text fields.
+            BLOBs and long text fields, with the
+            <literal>DYNAMIC</literal> row format.
           </para>
         </listitem>
 

@@ -596,13 +598,13 @@
       </bridgehead>
 
       <para>
-        Even before completing your upgrade to MySQL 5.5, you can
-        preview whether your database server or application works
-        correctly with InnoDB as the default storage engine. To set up
-        InnoDB as the default storage engine with an earlier MySQL
-        release, either specify on the command line
-        <literal>--default-storage-engine=InnoDB</literal>, or add to
-        your <literal>my.cnf</literal> file
+        Even before completing your upgrade from MySQL 5.1 or earlier to
+        MySQL 5.5 or higher, you can preview whether your database
+        server or application works correctly with InnoDB as the default
+        storage engine. To set up InnoDB as the default storage engine
+        with an earlier MySQL release, either specify on the command
+        line <literal>--default-storage-engine=InnoDB</literal>, or add
+        to your <literal>my.cnf</literal> file
         <literal>default-storage-engine=innodb</literal> in the
         <literal>[mysqld]</literal> section, then restart the server.
       </para>

@@ -621,7 +623,7 @@
       </para>
 
       <para>
-        If you didn't make a deliberate decision about the storage
+        If you did not make a deliberate decision about the storage
         engine, and you just want to preview how certain tables work
         when they're created under InnoDB, issue the command
         <literal>ALTER TABLE table_name ENGINE=InnoDB;</literal> for

@@ -629,16 +631,15 @@
         disturbing the original table, make a copy like so:
       </para>
 
-      <para>
-        <literal>CREATE TABLE InnoDB_Table (...) ENGINE=InnoDB AS SELECT
-        * FROM MyISAM_Table;</literal>
-      </para>
+<programlisting>
+CREATE TABLE InnoDB_Table (...) ENGINE=InnoDB AS SELECT * FROM MyISAM_Table;
+				</programlisting>
 
       <para>
-        Since there are so many performance enhancements in the InnoDB
-        that is part of MySQL 5.5, to get a true idea of the performance
-        with a full application under a realistic workload, install the
-        real MySQL 5.5 and run benchmarks.
+        Since there are so many performance enhancements in InnoDB in
+        MySQL 5.5 and higher, to get a true idea of the performance with
+        a full application under a realistic workload, install the
+        latest MySQL server and run benchmarks.
       </para>
 
       <para>

@@ -662,7 +663,7 @@
       <para>
         To know what the status of InnoDB is, whether you're doing
         what-if testing with an older MySQL or comprehensive testing
-        with MySQL 5.5:
+        with the latest MySQL:
       </para>
 
       <itemizedlist>


Thread
svn commit - mysqldoc@oter02: r25788 - trunk/refman-5.6john.russell7 Apr