List:Commits« Previous MessageNext Message »
From:mcbrown Date:January 3 2007 12:01pm
Subject:svn commit - mysqldoc@docsrva: r4365 - in trunk: refman-5.0 refman-5.1
View as plain text  
Author: mcbrown
Date: 2007-01-03 13:01:02 +0100 (Wed, 03 Jan 2007)
New Revision: 4365

Log:
Documenting Docs Bug: #25194



Modified:
   trunk/refman-5.0/se-federated.xml
   trunk/refman-5.1/se-federated.xml


Modified: trunk/refman-5.0/se-federated.xml
===================================================================
--- trunk/refman-5.0/se-federated.xml	2007-01-03 11:42:27 UTC (rev 4364)
+++ trunk/refman-5.0/se-federated.xml	2007-01-03 12:01:02 UTC (rev 4365)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 960 bytes

@@ -326,6 +326,17 @@
 
       <listitem>
         <para>
+          Performance on a <literal>FEDERATED</literal> table when
+          performing bulk inserts (for example, on a <literal>INSERT
+          INTO ... SELECT ...</literal> statement) is slower than with
+          other table types because each selected row is treated as an
+          individual <literal>INSERT</literal> statement on the
+          federated table.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           There is no way for the <literal>FEDERATED</literal> engine to
           know if the remote table has changed. The reason for this is
           that this table must work like a data file that would never be


Modified: trunk/refman-5.1/se-federated.xml
===================================================================
--- trunk/refman-5.1/se-federated.xml	2007-01-03 11:42:27 UTC (rev 4364)
+++ trunk/refman-5.1/se-federated.xml	2007-01-03 12:01:02 UTC (rev 4365)
Changed blocks: 1, Lines Added: 11, Lines Deleted: 0; 825 bytes

@@ -321,6 +321,17 @@
 
       <listitem>
         <para>
+          Performance on a <literal>FEDERATED</literal> table when
+          performing bulk inserts (for example, on a <literal>INSERT
+          INTO ... SELECT ...</literal> statement) is slower than with
+          other table types because each selected row is treated as an
+          individual <literal>INSERT</literal> statement on the
+          federated table.
+        </para>
+      </listitem>
+
+      <listitem>
+        <para>
           There is no support for transactions.
         </para>
       </listitem>


Thread
svn commit - mysqldoc@docsrva: r4365 - in trunk: refman-5.0 refman-5.1mcbrown3 Jan