List:Commits« Previous MessageNext Message »
From:john.russell Date:April 1 2011 7:41pm
Subject:svn commit - mysqldoc@oter02: r25680 - trunk/refman-5.6
View as plain text  
Author: jdrussel
Date: 2011-04-01 21:41:30 +0200 (Fri, 01 Apr 2011)
New Revision: 25680

Log:
Incorporated the material from innodb-introduction.xml in the InnoDB doc into the
chapter intro.


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-01 18:50:45 UTC (rev 25679)
+++ trunk/refman-5.6/se-innodb-core.xml	2011-04-01 19:41:30 UTC (rev 25680)
Changed blocks: 4, Lines Added: 73, Lines Deleted: 34; 4972 bytes

@@ -96,6 +96,70 @@
       </para>
     </listitem>
 
+    <listitem>
+      <para>
+        The latest InnoDB offers significant new features over MySQL 5.1
+        and earlier. These features focus on performance and
+        scalability, reliability, flexibility, and usability:
+      </para>
+
+      <itemizedlist>
+
+        <listitem>
+          <para>
+            <link linkend="innodb-create-index">Fast index creation: add
+            or drop indexes without copying the data</link>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <link linkend="innodb-compression">Data compression: shrink
+            tables, to significantly reduce storage and i/o</link>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <link linkend="innodb-row-format">New row format: fully
+            off-page storage of long <literal>BLOB</literal>,
+            <literal>TEXT</literal>, and <literal>VARCHAR</literal>
+            columns</link>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <link linkend="innodb-file-format">File format management:
+            protects upward and downward compatibility</link>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <link linkend="innodb-information-schema"><literal>INFORMATION_SCHEMA</literal>
+            tables: information about compression and locking</link>
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <link linkend="innodb-performance">Performance and
+            scalability enhancements</link> such as multiple background
+            I/O threads, multiple buffer pools, and group commit.
+          </para>
+        </listitem>
+
+        <listitem>
+          <para>
+            <link linkend="innodb-other-changes">Other changes for
+            flexibility, ease of use and reliability</link>
+          </para>
+        </listitem>
+
+      </itemizedlist>
+    </listitem>
+
   </itemizedlist>
 
   <para>

@@ -117,13 +181,15 @@
 
   <para>
     The <literal>InnoDB</literal> storage engine maintains its own
-    buffer pool for caching data and indexes in main memory.
-    <literal>InnoDB</literal> stores its tables and indexes in a
-    tablespace, which may consist of several files (or raw disk
-    partitions). This is different from, for example,
-    <literal>MyISAM</literal> tables where each table is stored using
-    separate files. <literal>InnoDB</literal> tables can be very large
-    even on operating systems where file size is limited to 2GB.
+    <link linkend="glos_buffer_pool">buffer pool</link> for caching data
+    and indexes in main memory. By default, <literal>InnoDB</literal>
+    stores all its tables and indexes in the single
+    <link linkend="glos_tablespace">system tablespace</link>, which may
+    consist of several files (or raw disk partitions). With the
+    file-per-table setting enabled, each new <literal>InnoDB</literal>
+    table is stored in a separate file. <literal>InnoDB</literal> tables
+    can handle large quantities of data, even on operating systems where
+    file size is limited to 2GB.
   </para>
 
   <para>

@@ -147,30 +213,6 @@
 
     <listitem>
       <para>
-        The InnoDB storage engine in MySQL &current-series; releases
-        includes a number performance improvements that in MySQL 5.1
-        were only available by installing the InnoDB Plugin. This latest
-        InnoDB (now known as InnoDB 1.1) offers new features, improved
-        performance and scalability, enhanced reliability and new
-        capabilities for flexibility and ease of use. Among the top
-        features are Fast Index Creation, table and index compression,
-        file format management, new
-        <literal>INFORMATION_SCHEMA</literal> tables, capacity tuning,
-        multiple background I/O threads, multiple buffer pools, and
-        group commit.
-      </para>
-
-<!-- JDR: strange that this reference goes to the standalone InnoDB manual rather than the same content
-brought into the Ref Man via Arby. -->
-
-      <para>
-        For information about these features, see
-        <xref linkend="innodb-5-5"/>.
-      </para>
-    </listitem>
-
-    <listitem>
-      <para>
         The MySQL Enterprise Backup product lets you back up a running
         MySQL database, including <literal>InnoDB</literal> and
         <literal>MyISAM</literal> tables, with minimal disruption to

@@ -621,9 +663,6 @@
 
     </itemizedlist>
 
-<!-- JDR: commenting out until I've done some local test builds and reorged the content. -->
-<!-- <xi:include href="innodb-introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> -->
-
   </section>
 
   <section id="innodb-configuration">


Thread
svn commit - mysqldoc@oter02: r25680 - trunk/refman-5.6john.russell1 Apr