Author: paul
Date: 2007-07-23 22:29:24 +0200 (Mon, 23 Jul 2007)
New Revision: 7184
Log:
r27850@polar: paul | 2007-07-23 12:56:17 -0500
Some cleanup of FEDERATED-limitations section.
Modified:
trunk/refman-5.0/se-federated.xml
trunk/refman-5.1/se-federated.xml
trunk/refman-5.2/se-federated.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27800
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22908
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:27850
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:22908
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:18941
Modified: trunk/refman-5.0/se-federated.xml
===================================================================
--- trunk/refman-5.0/se-federated.xml 2007-07-23 13:07:58 UTC (rev 7183)
+++ trunk/refman-5.0/se-federated.xml 2007-07-23 20:29:24 UTC (rev 7184)
Changed blocks: 5, Lines Added: 16, Lines Deleted: 15; 3399 bytes
@@ -323,8 +323,8 @@
<listitem>
<para>
A <literal>FEDERATED</literal> table does not support indexes
- per-se, since the access to the table is handled remotely, it
- is the remote table that supports the indexes. Care should be
+ per se. Because access to the table is handled remotely, it is
+ the remote table that supports the indexes. Care should be
taken when creating a <literal>FEDERATED</literal> table since
the index definition from an equivalent
<literal>MyISAM</literal> or other table may not be supported.
@@ -355,13 +355,21 @@
<listitem>
<para>
+ Internally, implementation uses <literal>SELECT</literal>,
+ <literal>INSERT</literal>, <literal>UPDATE</literal>, and
+ <literal>DELETE</literal>, but not <literal>HANDLER</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>FEDERATED</literal> storage engine supports
<literal>SELECT</literal>, <literal>INSERT</literal>,
<literal>UPDATE</literal>, <literal>DELETE</literal>, and
indexes. It does not support <literal>ALTER TABLE</literal>,
or any Data Definition Language statements other than
<literal>DROP TABLE</literal>. The current implementation does
- not use Prepared statements.
+ not use prepared statements.
<remark>
It remains to be seen whether the limited subset of the
@@ -405,7 +413,8 @@
As of MySQL 5.0.46, <literal>FEDERATED</literal> performs
bulk-insert handling such that multiple rows are sent to the
remote table in a batch. This provides a performance
- improvement and enables the remote table to perform statement
+ improvement. Also, if the remote table is transactional, it
+ enables the remote storage engine to perform statement
rollback properly should an error occur. This capability has
the following limitations:
</para>
@@ -436,9 +445,9 @@
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
- written to by anything other than the database. The integrity
- of the data in the local table could be breached if there was
- any change to the remote database.
+ written to by anything other than the database system. The
+ integrity of the data in the local table could be breached if
+ there was any change to the remote database.
</para>
</listitem>
@@ -452,14 +461,6 @@
<listitem>
<para>
- The implementation uses <literal>SELECT</literal>,
- <literal>INSERT</literal>, <literal>UPDATE</literal>, and
- <literal>DELETE</literal>, but not <literal>HANDLER</literal>.
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>FEDERATED</literal> tables do not work with the query
cache.
</para>
Modified: trunk/refman-5.1/se-federated.xml
===================================================================
--- trunk/refman-5.1/se-federated.xml 2007-07-23 13:07:58 UTC (rev 7183)
+++ trunk/refman-5.1/se-federated.xml 2007-07-23 20:29:24 UTC (rev 7184)
Changed blocks: 5, Lines Added: 17, Lines Deleted: 15; 3089 bytes
@@ -560,8 +560,8 @@
<listitem>
<para>
A <literal>FEDERATED</literal> table does not support indexes
- per-se, since the access to the table is handled remotely, it
- is the remote table that supports the indexes. Care should be
+ per se. Because access to the table is handled remotely, it is
+ the remote table that supports the indexes. Care should be
taken when creating a <literal>FEDERATED</literal> table since
the index definition from an equivalent
<literal>MyISAM</literal> or other table may not be supported.
@@ -592,6 +592,14 @@
<listitem>
<para>
+ Internally, implementation uses <literal>SELECT</literal>,
+ <literal>INSERT</literal>, <literal>UPDATE</literal>, and
+ <literal>DELETE</literal>, but not <literal>HANDLER</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>FEDERATED</literal> storage engine supports
<literal>SELECT</literal>, <literal>INSERT</literal>,
<literal>UPDATE</literal>, <literal>DELETE</literal>,
@@ -650,8 +658,10 @@
bulk-insert handling such that multiple rows are sent to the
remote table in a batch. This provides a performance
improvement and enables the the remote table to perform
- statement rollback properly should an error occur. This
- capability has the following limitations:
+ improvement. Also, if the remote table is transactional, it
+ enables the remote storage engine to perform statement
+ rollback properly should an error occur. This capability has
+ the following limitations:
</para>
<itemizedlist>
@@ -680,9 +690,9 @@
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
- written to by anything other than the database. The integrity
- of the data in the local table could be breached if there was
- any change to the remote database.
+ written to by anything other than the database system. The
+ integrity of the data in the local table could be breached if
+ there was any change to the remote database.
</para>
</listitem>
@@ -713,14 +723,6 @@
<listitem>
<para>
- The implementation uses <literal>SELECT</literal>,
- <literal>INSERT</literal>, <literal>UPDATE</literal>, and
- <literal>DELETE</literal>, but not <literal>HANDLER</literal>.
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>FEDERATED</literal> tables do not work with the query
cache.
</para>
Modified: trunk/refman-5.2/se-federated.xml
===================================================================
--- trunk/refman-5.2/se-federated.xml 2007-07-23 13:07:58 UTC (rev 7183)
+++ trunk/refman-5.2/se-federated.xml 2007-07-23 20:29:24 UTC (rev 7184)
Changed blocks: 5, Lines Added: 16, Lines Deleted: 16; 3192 bytes
@@ -560,8 +560,8 @@
<listitem>
<para>
A <literal>FEDERATED</literal> table does not support indexes
- per-se, since the access to the table is handled remotely, it
- is the remote table that supports the indexes. Care should be
+ per se. Because access to the table is handled remotely, it is
+ the remote table that supports the indexes. Care should be
taken when creating a <literal>FEDERATED</literal> table since
the index definition from an equivalent
<literal>MyISAM</literal> or other table may not be supported.
@@ -592,6 +592,14 @@
<listitem>
<para>
+ Internally, implementation uses <literal>SELECT</literal>,
+ <literal>INSERT</literal>, <literal>UPDATE</literal>, and
+ <literal>DELETE</literal>, but not <literal>HANDLER</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
The <literal>FEDERATED</literal> storage engine supports
<literal>SELECT</literal>, <literal>INSERT</literal>,
<literal>UPDATE</literal>, <literal>DELETE</literal>,
@@ -639,9 +647,9 @@
For a multiple-row insert into a <literal>FEDERATED</literal>
table, the storage engine performs bulk-insert handling such
that multiple rows are sent to the remote table in a batch.
- This provides a performance improvement and, if the remote
- table is transactional, enables the the remote table to
- perform statement rollback properly should an error occur.
+ This provides a performance improvement. Also, if the remote
+ table is transactional, it enables the remote storage engine
+ to perform statement rollback properly should an error occur.
This capability has the following limitations:
</para>
@@ -674,9 +682,9 @@
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
- written to by anything other than the database. The integrity
- of the data in the local table could be breached if there was
- any change to the remote database.
+ written to by anything other than the database system. The
+ integrity of the data in the local table could be breached if
+ there was any change to the remote database.
</para>
</listitem>
@@ -707,14 +715,6 @@
<listitem>
<para>
- The implementation uses <literal>SELECT</literal>,
- <literal>INSERT</literal>, <literal>UPDATE</literal>, and
- <literal>DELETE</literal>, but not <literal>HANDLER</literal>.
- </para>
- </listitem>
-
- <listitem>
- <para>
<literal>FEDERATED</literal> tables do not work with the query
cache.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7184 - in trunk: . refman-5.0 refman-5.1 refman-5.2 | paul | 23 Jul |
