svn commit - mysqldoc@oter02: r25561 - trunk/innodb-1.1

[john.russell]

Author: jdrussel
Date: 2011-03-25 22:49:17 +0100 (Fri, 25 Mar 2011)
New Revision: 25561

Log:
Add more introductory info about the file-format feature.
Make less InnoDB-centric.
Scope out some examples that can mark the end of the "beginner/intermediate" part of the chapter.


Modified:
   trunk/innodb-1.1/innodb-file-format.xml


Modified: trunk/innodb-1.1/innodb-file-format.xml
===================================================================
--- trunk/innodb-1.1/innodb-file-format.xml	2011-03-25 21:35:44 UTC (rev 25560)
+++ trunk/innodb-1.1/innodb-file-format.xml	2011-03-25 21:49:17 UTC (rev 25561)
Changed blocks: 4, Lines Added: 27, Lines Deleted: 11; 2941 bytes

@@ -27,24 +27,29 @@
 
   <para>
     As InnoDB evolves, new on-disk data structures are sometimes
-    required to support new features. Compressed tables (see
-    <xref linkend="innodb-compression"/>), and long variable-length
+    required to support new features. Features such as compressed tables
+    (see <xref linkend="innodb-compression"/>), and long variable-length
     columns stored off-page (see <xref linkend="innodb-row-format"/>)
-    are new features requiring data file formats that are not compatible
-    with prior versions of InnoDB. These features both require use of
-    the new <link
-			linkend="glos_barracuda">Barracuda</link> file
-    format.
+    require data file formats that are not compatible with prior
+    versions of InnoDB. These features both require use of the new
+    <link
+			linkend="glos_barracuda">Barracuda</link> file format.
   </para>
 
   <note>
     <para>
-      The other new features are compatible with the original
+      All other new features are compatible with the original
       <link linkend="glos_antelope">Antelope</link> file format and do
       not require the Barracuda file format.
     </para>
   </note>
 
+  <para>
+    This section discusses how to specify the file format for new InnoDB
+    tables, compatibility of different file formats between MySQL
+    releases,
+  </para>
+
   <bridgehead>
     Named File Formats
   </bridgehead>

@@ -69,6 +74,13 @@
 
 <!-- JDR: too short; add links, move examples here, show in the context of CREATE TABLE -->
 
+<!-- JDR: examples...
+- create Barracuda table (row_format=compressed)
+- show error for same table with Antelope
+- create Barracuda table (file-per-table)
+- show same table works OK with Antelope
+-->
+
     <title>Enabling File Formats</title>
 
     <para>

@@ -79,11 +91,15 @@
       TABLE</literal> and <literal
 			role="stmt">ALTER TABLE</literal>
       can be used to create tables that depend on support for the
-      Barracuda file format.
+      <link linkend="glos_barracuda">Barracuda</link> file format.
     </para>
 
     <para>
-      In MySQL 5.5.5 and higher, the default value is Barracuda.
+      Although Oracle recommends using the Barracuda format for new
+      tables where practical, in MySQL &current-series; the default file
+      format is still <link linkend="glos_antelope">Antelope</link>, for
+      maximum compatibility with replication configurations containing
+      different MySQL releases.
     </para>
 
     <para>

@@ -99,7 +115,7 @@
 
 <!-- JDR: maybe move earlier compatibility sections here -->
 
-    <title>File Format Compatibility</title>
+    <title>Verifying File Format Compatibility</title>
 
     <indexterm>
       <primary>ib-file set</primary>