svn commit - mysqldoc@oter02: r25114 - in trunk: refman-5.0 refman-5.1 refman-5.5 refman-5.6 refman-6.0

[tony.bedford]

Author: ab226828
Date: 2011-02-17 18:07:30 +0100 (Thu, 17 Feb 2011)
New Revision: 25114

Log:
Clarified note on Federated engine

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


Modified: trunk/refman-5.0/se-federated.xml
===================================================================
--- trunk/refman-5.0/se-federated.xml	2011-02-16 23:03:58 UTC (rev 25113)
+++ trunk/refman-5.0/se-federated.xml	2011-02-17 17:07:30 UTC (rev 25114)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 6; 1203 bytes

@@ -234,13 +234,12 @@
       <para>
         You can improve the performance of a
         <literal>FEDERATED</literal> table by adding indexes to the
-        table on the host, even though the tables will not actually be
-        created locally. The optimization will occur because the query
+        table on the host. The optimization will occur because the query
         sent to the remote server will include the contents of the
-        <literal>WHERE</literal> clause will be sent to the remote
-        server and executed locally. This reduces the network traffic
-        that would otherwise request the entire table from the server
-        for local processing.
+        <literal>WHERE</literal> clause and will be sent to the remote
+        server and subsequently executed locally. This reduces the
+        network traffic that would otherwise request the entire table
+        from the server for local processing.
       </para>
     </note>
 


Modified: trunk/refman-5.1/se-federated.xml
===================================================================
--- trunk/refman-5.1/se-federated.xml	2011-02-16 23:03:58 UTC (rev 25113)
+++ trunk/refman-5.1/se-federated.xml	2011-02-17 17:07:30 UTC (rev 25114)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 6; 1203 bytes

@@ -242,13 +242,12 @@
       <para>
         You can improve the performance of a
         <literal>FEDERATED</literal> table by adding indexes to the
-        table on the host, even though the tables will not actually be
-        created locally. The optimization will occur because the query
+        table on the host. The optimization will occur because the query
         sent to the remote server will include the contents of the
-        <literal>WHERE</literal> clause will be sent to the remote
-        server and executed locally. This reduces the network traffic
-        that would otherwise request the entire table from the server
-        for local processing.
+        <literal>WHERE</literal> clause and will be sent to the remote
+        server and subsequently executed locally. This reduces the
+        network traffic that would otherwise request the entire table
+        from the server for local processing.
       </para>
     </note>
 


Modified: trunk/refman-5.5/se-federated.xml
===================================================================
--- trunk/refman-5.5/se-federated.xml	2011-02-16 23:03:58 UTC (rev 25113)
+++ trunk/refman-5.5/se-federated.xml	2011-02-17 17:07:30 UTC (rev 25114)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 6; 1203 bytes

@@ -244,13 +244,12 @@
       <para>
         You can improve the performance of a
         <literal>FEDERATED</literal> table by adding indexes to the
-        table on the host, even though the tables will not actually be
-        created locally. The optimization will occur because the query
+        table on the host. The optimization will occur because the query
         sent to the remote server will include the contents of the
-        <literal>WHERE</literal> clause will be sent to the remote
-        server and executed locally. This reduces the network traffic
-        that would otherwise request the entire table from the server
-        for local processing.
+        <literal>WHERE</literal> clause and will be sent to the remote
+        server and subsequently executed locally. This reduces the
+        network traffic that would otherwise request the entire table
+        from the server for local processing.
       </para>
     </note>
 


Modified: trunk/refman-5.6/se-federated.xml
===================================================================
--- trunk/refman-5.6/se-federated.xml	2011-02-16 23:03:58 UTC (rev 25113)
+++ trunk/refman-5.6/se-federated.xml	2011-02-17 17:07:30 UTC (rev 25114)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 6; 1203 bytes

@@ -244,13 +244,12 @@
       <para>
         You can improve the performance of a
         <literal>FEDERATED</literal> table by adding indexes to the
-        table on the host, even though the tables will not actually be
-        created locally. The optimization will occur because the query
+        table on the host. The optimization will occur because the query
         sent to the remote server will include the contents of the
-        <literal>WHERE</literal> clause will be sent to the remote
-        server and executed locally. This reduces the network traffic
-        that would otherwise request the entire table from the server
-        for local processing.
+        <literal>WHERE</literal> clause and will be sent to the remote
+        server and subsequently executed locally. This reduces the
+        network traffic that would otherwise request the entire table
+        from the server for local processing.
       </para>
     </note>
 


Modified: trunk/refman-6.0/se-federated.xml
===================================================================
--- trunk/refman-6.0/se-federated.xml	2011-02-16 23:03:58 UTC (rev 25113)
+++ trunk/refman-6.0/se-federated.xml	2011-02-17 17:07:30 UTC (rev 25114)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 6; 1203 bytes

@@ -242,13 +242,12 @@
       <para>
         You can improve the performance of a
         <literal>FEDERATED</literal> table by adding indexes to the
-        table on the host, even though the tables will not actually be
-        created locally. The optimization will occur because the query
+        table on the host. The optimization will occur because the query
         sent to the remote server will include the contents of the
-        <literal>WHERE</literal> clause will be sent to the remote
-        server and executed locally. This reduces the network traffic
-        that would otherwise request the entire table from the server
-        for local processing.
+        <literal>WHERE</literal> clause and will be sent to the remote
+        server and subsequently executed locally. This reduces the
+        network traffic that would otherwise request the entire table
+        from the server for local processing.
       </para>
     </note>