List:Commits« Previous MessageNext Message »
From:jon.stephens Date:March 4 2011 4:56pm
Subject:svn commit - mysqldoc@oter02: r25265 - in trunk: refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0
View as plain text  
Author: js221926
Date: 2011-03-04 17:56:22 +0100 (Fri, 04 Mar 2011)
New Revision: 25265

Log:

Fix typo

Big nested important note -- De-gunk, make formalpara, add ID

Add link in 5.1/Cluster version



Modified:
   trunk/refman-5.0/se-memory.xml
   trunk/refman-5.1/mysql-cluster-overview.xml
   trunk/refman-5.1/se-memory-core.xml
   trunk/refman-5.5/se-memory-core.xml
   trunk/refman-5.6/se-memory-core.xml
   trunk/refman-6.0/se-memory-core.xml


Modified: trunk/refman-5.0/se-memory.xml
===================================================================
--- trunk/refman-5.0/se-memory.xml	2011-03-04 16:47:37 UTC (rev 25264)
+++ trunk/refman-5.0/se-memory.xml	2011-03-04 16:56:22 UTC (rev 25265)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 597 bytes

@@ -34,7 +34,7 @@
   </para>
 
   <para>
-    The <literal>MEMORY</literal> storage engine associate each table
+    The <literal>MEMORY</literal> storage engine associates each table
     with one disk file. The file name begins with the table name and has
     an extension of <filename>.frm</filename> to indicate that it stores
     the table definition.


Modified: trunk/refman-5.1/mysql-cluster-overview.xml
===================================================================
--- trunk/refman-5.1/mysql-cluster-overview.xml	2011-03-04 16:47:37 UTC (rev 25264)
+++ trunk/refman-5.1/mysql-cluster-overview.xml	2011-03-04 16:56:22 UTC (rev 25265)
Changed blocks: 1, Lines Added: 7, Lines Deleted: 0; 694 bytes

@@ -4905,6 +4905,13 @@
     </para>
 
     <para>
+      For information about the relative characteristics of the
+      <literal role="se">NDB</literal> and
+      <literal role="se">MEMORY</literal> storage engines, see
+      <xref linkend="memory-compared-cluster"/>.
+    </para>
+
+    <para>
       See <xref linkend="storage-engines"/>, for additional information
       about MySQL storage engines.
     </para>


Modified: trunk/refman-5.1/se-memory-core.xml
===================================================================
--- trunk/refman-5.1/se-memory-core.xml	2011-03-04 16:47:37 UTC (rev 25264)
+++ trunk/refman-5.1/se-memory-core.xml	2011-03-04 16:56:22 UTC (rev 25265)
Changed blocks: 2, Lines Added: 87, Lines Deleted: 85; 6643 bytes

@@ -40,7 +40,10 @@
     Features</citetitle>
   </para>
 
-  <important>
+  <formalpara id="memory-compared-cluster">
+
+    <title><literal>MEMORY</literal> compared with MySQL Cluster</title>
+
     <para>
       Developers looking to deploy applications that use the
       <literal role="se">MEMORY</literal> storage engine should consider

@@ -49,107 +52,106 @@
       characteristics:
     </para>
 
-    <itemizedlist>
+  </formalpara>
 
-      <listitem>
-        <para>
-          Operations such as session management or caching
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          In-memory storage for fast access and low latency
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Operations such as session management or caching
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          A read-only or read-mostly data access pattern (limited
-          updates)
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        In-memory storage for fast access and low latency
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        A read-only or read-mostly data access pattern (limited updates)
+      </para>
+    </listitem>
 
-    <para>
-      However, <literal role="se">MEMORY</literal> performance is
-      constrained by contention resulting from single-thread execution
-      and table lock overhead when processing updates. This limits
-      scalability when load increases, particularly for statement mixes
-      that include writes. Also, <literal role="se">MEMORY</literal>
-      does not preserve table contents across server restarts.
-    </para>
+  </itemizedlist>
 
-    <para>
-      MySQL Cluster offers the same features as the
-      <literal role="se">MEMORY</literal> engine with higher performance
-      levels, and provides additional features not available with
-      <literal role="se">MEMORY</literal>:
-    </para>
+  <para>
+    However, <literal role="se">MEMORY</literal> performance is
+    constrained by contention resulting from single-thread execution and
+    table lock overhead when processing updates. This limits scalability
+    when load increases, particularly for statement mixes that include
+    writes. Also, <literal role="se">MEMORY</literal> does not preserve
+    table contents across server restarts.
+  </para>
 
-    <itemizedlist>
+  <para>
+    MySQL Cluster offers the same features as the
+    <literal role="se">MEMORY</literal> engine with higher performance
+    levels, and provides additional features not available with
+    <literal role="se">MEMORY</literal>:
+  </para>
 
-      <listitem>
-        <para>
-          Row-level locking and multiple-thread operation for low
-          contention between clients
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          Scalability even with statement mixes that include writes
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Row-level locking and multiple-thread operation for low
+        contention between clients
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Optional disk-backed operation for data durability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Scalability even with statement mixes that include writes
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Shared-nothing architecture and multiple-host operation with
-          no single point of failure, enabling 99.999% availability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Optional disk-backed operation for data durability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Automatic data distribution across nodes; application
-          developers need not craft custom sharding or partitioning
-          solutions
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Shared-nothing architecture and multiple-host operation with no
+        single point of failure, enabling 99.999% availability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Support for variable-length data types (including
-          <literal role="type">BLOB</literal> and
-          <literal role="type">TEXT</literal>) not supported by
-          <literal role="se">MEMORY</literal>
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Automatic data distribution across nodes; application developers
+        need not craft custom sharding or partitioning solutions
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        Support for variable-length data types (including
+        <literal role="type">BLOB</literal> and
+        <literal role="type">TEXT</literal>) not supported by
+        <literal role="se">MEMORY</literal>
+      </para>
+    </listitem>
 
-    <para>
-      For a white paper with more detailed comparison of the
-      <literal role="se">MEMORY</literal> storage engine and MySQL
-      Cluster, see
-      <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
-      Web Services with MySQL Cluster: An Alternative to the MySQL
-      Memory Storage Engine</ulink>. This white paper includes a
-      performance study of the two technologies and a step-by-step guide
-      describing how existing <literal role="se">MEMORY</literal> users
-      can migrate to MySQL Cluster.
-    </para>
-  </important>
+  </itemizedlist>
 
   <para>
-    The <literal>MEMORY</literal> storage engine associate each table
+    For a white paper with more detailed comparison of the
+    <literal role="se">MEMORY</literal> storage engine and MySQL
+    Cluster, see
+    <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
+    Web Services with MySQL Cluster: An Alternative to the MySQL Memory
+    Storage Engine</ulink>. This white paper includes a performance
+    study of the two technologies and a step-by-step guide describing
+    how existing <literal role="se">MEMORY</literal> users can migrate
+    to MySQL Cluster.
+  </para>
+
+  <para>
+    The <literal>MEMORY</literal> storage engine associates each table
     with one disk file. The file name begins with the table name and has
     an extension of <filename>.frm</filename> to indicate that it stores
     the table definition.


Modified: trunk/refman-5.5/se-memory-core.xml
===================================================================
--- trunk/refman-5.5/se-memory-core.xml	2011-03-04 16:47:37 UTC (rev 25264)
+++ trunk/refman-5.5/se-memory-core.xml	2011-03-04 16:56:22 UTC (rev 25265)
Changed blocks: 2, Lines Added: 87, Lines Deleted: 85; 6643 bytes

@@ -40,7 +40,10 @@
     Features</citetitle>
   </para>
 
-  <important>
+  <formalpara id="memory-compared-cluster">
+
+    <title><literal>MEMORY</literal> compared with MySQL Cluster</title>
+
     <para>
       Developers looking to deploy applications that use the
       <literal role="se">MEMORY</literal> storage engine should consider

@@ -49,107 +52,106 @@
       characteristics:
     </para>
 
-    <itemizedlist>
+  </formalpara>
 
-      <listitem>
-        <para>
-          Operations such as session management or caching
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          In-memory storage for fast access and low latency
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Operations such as session management or caching
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          A read-only or read-mostly data access pattern (limited
-          updates)
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        In-memory storage for fast access and low latency
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        A read-only or read-mostly data access pattern (limited updates)
+      </para>
+    </listitem>
 
-    <para>
-      However, <literal role="se">MEMORY</literal> performance is
-      constrained by contention resulting from single-thread execution
-      and table lock overhead when processing updates. This limits
-      scalability when load increases, particularly for statement mixes
-      that include writes. Also, <literal role="se">MEMORY</literal>
-      does not preserve table contents across server restarts.
-    </para>
+  </itemizedlist>
 
-    <para>
-      MySQL Cluster offers the same features as the
-      <literal role="se">MEMORY</literal> engine with higher performance
-      levels, and provides additional features not available with
-      <literal role="se">MEMORY</literal>:
-    </para>
+  <para>
+    However, <literal role="se">MEMORY</literal> performance is
+    constrained by contention resulting from single-thread execution and
+    table lock overhead when processing updates. This limits scalability
+    when load increases, particularly for statement mixes that include
+    writes. Also, <literal role="se">MEMORY</literal> does not preserve
+    table contents across server restarts.
+  </para>
 
-    <itemizedlist>
+  <para>
+    MySQL Cluster offers the same features as the
+    <literal role="se">MEMORY</literal> engine with higher performance
+    levels, and provides additional features not available with
+    <literal role="se">MEMORY</literal>:
+  </para>
 
-      <listitem>
-        <para>
-          Row-level locking and multiple-thread operation for low
-          contention between clients
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          Scalability even with statement mixes that include writes
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Row-level locking and multiple-thread operation for low
+        contention between clients
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Optional disk-backed operation for data durability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Scalability even with statement mixes that include writes
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Shared-nothing architecture and multiple-host operation with
-          no single point of failure, enabling 99.999% availability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Optional disk-backed operation for data durability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Automatic data distribution across nodes; application
-          developers need not craft custom sharding or partitioning
-          solutions
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Shared-nothing architecture and multiple-host operation with no
+        single point of failure, enabling 99.999% availability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Support for variable-length data types (including
-          <literal role="type">BLOB</literal> and
-          <literal role="type">TEXT</literal>) not supported by
-          <literal role="se">MEMORY</literal>
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Automatic data distribution across nodes; application developers
+        need not craft custom sharding or partitioning solutions
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        Support for variable-length data types (including
+        <literal role="type">BLOB</literal> and
+        <literal role="type">TEXT</literal>) not supported by
+        <literal role="se">MEMORY</literal>
+      </para>
+    </listitem>
 
-    <para>
-      For a white paper with more detailed comparison of the
-      <literal role="se">MEMORY</literal> storage engine and MySQL
-      Cluster, see
-      <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
-      Web Services with MySQL Cluster: An Alternative to the MySQL
-      Memory Storage Engine</ulink>. This white paper includes a
-      performance study of the two technologies and a step-by-step guide
-      describing how existing <literal role="se">MEMORY</literal> users
-      can migrate to MySQL Cluster.
-    </para>
-  </important>
+  </itemizedlist>
 
   <para>
-    The <literal>MEMORY</literal> storage engine associate each table
+    For a white paper with more detailed comparison of the
+    <literal role="se">MEMORY</literal> storage engine and MySQL
+    Cluster, see
+    <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
+    Web Services with MySQL Cluster: An Alternative to the MySQL Memory
+    Storage Engine</ulink>. This white paper includes a performance
+    study of the two technologies and a step-by-step guide describing
+    how existing <literal role="se">MEMORY</literal> users can migrate
+    to MySQL Cluster.
+  </para>
+
+  <para>
+    The <literal>MEMORY</literal> storage engine associates each table
     with one disk file. The file name begins with the table name and has
     an extension of <filename>.frm</filename> to indicate that it stores
     the table definition.


Modified: trunk/refman-5.6/se-memory-core.xml
===================================================================
--- trunk/refman-5.6/se-memory-core.xml	2011-03-04 16:47:37 UTC (rev 25264)
+++ trunk/refman-5.6/se-memory-core.xml	2011-03-04 16:56:22 UTC (rev 25265)
Changed blocks: 2, Lines Added: 87, Lines Deleted: 85; 6643 bytes

@@ -40,7 +40,10 @@
     Features</citetitle>
   </para>
 
-  <important>
+  <formalpara id="memory-compared-cluster">
+
+    <title><literal>MEMORY</literal> compared with MySQL Cluster</title>
+
     <para>
       Developers looking to deploy applications that use the
       <literal role="se">MEMORY</literal> storage engine should consider

@@ -49,107 +52,106 @@
       characteristics:
     </para>
 
-    <itemizedlist>
+  </formalpara>
 
-      <listitem>
-        <para>
-          Operations such as session management or caching
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          In-memory storage for fast access and low latency
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Operations such as session management or caching
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          A read-only or read-mostly data access pattern (limited
-          updates)
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        In-memory storage for fast access and low latency
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        A read-only or read-mostly data access pattern (limited updates)
+      </para>
+    </listitem>
 
-    <para>
-      However, <literal role="se">MEMORY</literal> performance is
-      constrained by contention resulting from single-thread execution
-      and table lock overhead when processing updates. This limits
-      scalability when load increases, particularly for statement mixes
-      that include writes. Also, <literal role="se">MEMORY</literal>
-      does not preserve table contents across server restarts.
-    </para>
+  </itemizedlist>
 
-    <para>
-      MySQL Cluster offers the same features as the
-      <literal role="se">MEMORY</literal> engine with higher performance
-      levels, and provides additional features not available with
-      <literal role="se">MEMORY</literal>:
-    </para>
+  <para>
+    However, <literal role="se">MEMORY</literal> performance is
+    constrained by contention resulting from single-thread execution and
+    table lock overhead when processing updates. This limits scalability
+    when load increases, particularly for statement mixes that include
+    writes. Also, <literal role="se">MEMORY</literal> does not preserve
+    table contents across server restarts.
+  </para>
 
-    <itemizedlist>
+  <para>
+    MySQL Cluster offers the same features as the
+    <literal role="se">MEMORY</literal> engine with higher performance
+    levels, and provides additional features not available with
+    <literal role="se">MEMORY</literal>:
+  </para>
 
-      <listitem>
-        <para>
-          Row-level locking and multiple-thread operation for low
-          contention between clients
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          Scalability even with statement mixes that include writes
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Row-level locking and multiple-thread operation for low
+        contention between clients
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Optional disk-backed operation for data durability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Scalability even with statement mixes that include writes
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Shared-nothing architecture and multiple-host operation with
-          no single point of failure, enabling 99.999% availability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Optional disk-backed operation for data durability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Automatic data distribution across nodes; application
-          developers need not craft custom sharding or partitioning
-          solutions
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Shared-nothing architecture and multiple-host operation with no
+        single point of failure, enabling 99.999% availability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Support for variable-length data types (including
-          <literal role="type">BLOB</literal> and
-          <literal role="type">TEXT</literal>) not supported by
-          <literal role="se">MEMORY</literal>
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Automatic data distribution across nodes; application developers
+        need not craft custom sharding or partitioning solutions
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        Support for variable-length data types (including
+        <literal role="type">BLOB</literal> and
+        <literal role="type">TEXT</literal>) not supported by
+        <literal role="se">MEMORY</literal>
+      </para>
+    </listitem>
 
-    <para>
-      For a white paper with more detailed comparison of the
-      <literal role="se">MEMORY</literal> storage engine and MySQL
-      Cluster, see
-      <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
-      Web Services with MySQL Cluster: An Alternative to the MySQL
-      Memory Storage Engine</ulink>. This white paper includes a
-      performance study of the two technologies and a step-by-step guide
-      describing how existing <literal role="se">MEMORY</literal> users
-      can migrate to MySQL Cluster.
-    </para>
-  </important>
+  </itemizedlist>
 
   <para>
-    The <literal>MEMORY</literal> storage engine associate each table
+    For a white paper with more detailed comparison of the
+    <literal role="se">MEMORY</literal> storage engine and MySQL
+    Cluster, see
+    <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
+    Web Services with MySQL Cluster: An Alternative to the MySQL Memory
+    Storage Engine</ulink>. This white paper includes a performance
+    study of the two technologies and a step-by-step guide describing
+    how existing <literal role="se">MEMORY</literal> users can migrate
+    to MySQL Cluster.
+  </para>
+
+  <para>
+    The <literal>MEMORY</literal> storage engine associates each table
     with one disk file. The file name begins with the table name and has
     an extension of <filename>.frm</filename> to indicate that it stores
     the table definition.


Modified: trunk/refman-6.0/se-memory-core.xml
===================================================================
--- trunk/refman-6.0/se-memory-core.xml	2011-03-04 16:47:37 UTC (rev 25264)
+++ trunk/refman-6.0/se-memory-core.xml	2011-03-04 16:56:22 UTC (rev 25265)
Changed blocks: 2, Lines Added: 87, Lines Deleted: 85; 6643 bytes

@@ -40,7 +40,10 @@
     Features</citetitle>
   </para>
 
-  <important>
+  <formalpara id="memory-compared-cluster">
+
+    <title><literal>MEMORY</literal> compared with MySQL Cluster</title>
+
     <para>
       Developers looking to deploy applications that use the
       <literal role="se">MEMORY</literal> storage engine should consider

@@ -49,107 +52,106 @@
       characteristics:
     </para>
 
-    <itemizedlist>
+  </formalpara>
 
-      <listitem>
-        <para>
-          Operations such as session management or caching
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          In-memory storage for fast access and low latency
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Operations such as session management or caching
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          A read-only or read-mostly data access pattern (limited
-          updates)
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        In-memory storage for fast access and low latency
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        A read-only or read-mostly data access pattern (limited updates)
+      </para>
+    </listitem>
 
-    <para>
-      However, <literal role="se">MEMORY</literal> performance is
-      constrained by contention resulting from single-thread execution
-      and table lock overhead when processing updates. This limits
-      scalability when load increases, particularly for statement mixes
-      that include writes. Also, <literal role="se">MEMORY</literal>
-      does not preserve table contents across server restarts.
-    </para>
+  </itemizedlist>
 
-    <para>
-      MySQL Cluster offers the same features as the
-      <literal role="se">MEMORY</literal> engine with higher performance
-      levels, and provides additional features not available with
-      <literal role="se">MEMORY</literal>:
-    </para>
+  <para>
+    However, <literal role="se">MEMORY</literal> performance is
+    constrained by contention resulting from single-thread execution and
+    table lock overhead when processing updates. This limits scalability
+    when load increases, particularly for statement mixes that include
+    writes. Also, <literal role="se">MEMORY</literal> does not preserve
+    table contents across server restarts.
+  </para>
 
-    <itemizedlist>
+  <para>
+    MySQL Cluster offers the same features as the
+    <literal role="se">MEMORY</literal> engine with higher performance
+    levels, and provides additional features not available with
+    <literal role="se">MEMORY</literal>:
+  </para>
 
-      <listitem>
-        <para>
-          Row-level locking and multiple-thread operation for low
-          contention between clients
-        </para>
-      </listitem>
+  <itemizedlist>
 
-      <listitem>
-        <para>
-          Scalability even with statement mixes that include writes
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Row-level locking and multiple-thread operation for low
+        contention between clients
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Optional disk-backed operation for data durability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Scalability even with statement mixes that include writes
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Shared-nothing architecture and multiple-host operation with
-          no single point of failure, enabling 99.999% availability
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Optional disk-backed operation for data durability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Automatic data distribution across nodes; application
-          developers need not craft custom sharding or partitioning
-          solutions
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Shared-nothing architecture and multiple-host operation with no
+        single point of failure, enabling 99.999% availability
+      </para>
+    </listitem>
 
-      <listitem>
-        <para>
-          Support for variable-length data types (including
-          <literal role="type">BLOB</literal> and
-          <literal role="type">TEXT</literal>) not supported by
-          <literal role="se">MEMORY</literal>
-        </para>
-      </listitem>
+    <listitem>
+      <para>
+        Automatic data distribution across nodes; application developers
+        need not craft custom sharding or partitioning solutions
+      </para>
+    </listitem>
 
-    </itemizedlist>
+    <listitem>
+      <para>
+        Support for variable-length data types (including
+        <literal role="type">BLOB</literal> and
+        <literal role="type">TEXT</literal>) not supported by
+        <literal role="se">MEMORY</literal>
+      </para>
+    </listitem>
 
-    <para>
-      For a white paper with more detailed comparison of the
-      <literal role="se">MEMORY</literal> storage engine and MySQL
-      Cluster, see
-      <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
-      Web Services with MySQL Cluster: An Alternative to the MySQL
-      Memory Storage Engine</ulink>. This white paper includes a
-      performance study of the two technologies and a step-by-step guide
-      describing how existing <literal role="se">MEMORY</literal> users
-      can migrate to MySQL Cluster.
-    </para>
-  </important>
+  </itemizedlist>
 
   <para>
-    The <literal>MEMORY</literal> storage engine associate each table
+    For a white paper with more detailed comparison of the
+    <literal role="se">MEMORY</literal> storage engine and MySQL
+    Cluster, see
+    <ulink url="http://www.mysql.com/why-mysql/white-papers/mysql-wp_cluster-7.0_Cluster_MEMORY.php">Scaling
+    Web Services with MySQL Cluster: An Alternative to the MySQL Memory
+    Storage Engine</ulink>. This white paper includes a performance
+    study of the two technologies and a step-by-step guide describing
+    how existing <literal role="se">MEMORY</literal> users can migrate
+    to MySQL Cluster.
+  </para>
+
+  <para>
+    The <literal>MEMORY</literal> storage engine associates each table
     with one disk file. The file name begins with the table name and has
     an extension of <filename>.frm</filename> to indicate that it stores
     the table definition.


Thread
svn commit - mysqldoc@oter02: r25265 - in trunk: refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0jon.stephens4 Mar