Author: jstephens
Date: 2009-05-30 07:19:33 +0200 (Sat, 30 May 2009)
New Revision: 15132
Log:
Fixes Docs bugs:
Bug # 37532, Bug #44646
(Row counts for InnoDB tables in EXPLAIN output and I_S tables are not
exact)
Modified:
trunk/refman-4.1/optimization.xml
trunk/refman-5.0/information-schema.xml
trunk/refman-5.0/optimization.xml
trunk/refman-5.1/information-schema.xml
trunk/refman-5.1/optimization.xml
trunk/refman-5.4/information-schema.xml
trunk/refman-5.4/optimization.xml
trunk/refman-6.0/information-schema.xml
trunk/refman-6.0/optimization.xml
Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-4.1/optimization.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 642 bytes
@@ -1427,6 +1427,11 @@
The <literal>rows</literal> column indicates the number of
rows MySQL believes it must examine to execute the query.
</para>
+
+ <para>
+ For <literal role="se">InnoDB</literal> tables, this number
+ is an estimate, and may not always be exact.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.0/information-schema.xml
===================================================================
--- trunk/refman-5.0/information-schema.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-5.0/information-schema.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 1, Lines Added: 6, Lines Deleted: 3; 1007 bytes
@@ -651,11 +651,14 @@
<para>
The <literal>TABLE_ROWS</literal> column is
<literal>NULL</literal> if the table is in the
- <literal>INFORMATION_SCHEMA</literal> database. For
- <literal>InnoDB</literal> tables, the row count is only a
- rough estimate used in SQL optimization.
+ <literal>INFORMATION_SCHEMA</literal> database.
</para>
+ <para>
+ For <literal role="se">InnoDB</literal> tables, the row count
+ is only a rough estimate used in SQL optimization.
+ </para>
+
<remark role="todo">
TEMPORARY tables are missing at the moment; perhaps because
they don't appear in the output of SHOW TABLES, either?
Modified: trunk/refman-5.0/optimization.xml
===================================================================
--- trunk/refman-5.0/optimization.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-5.0/optimization.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 642 bytes
@@ -1445,6 +1445,11 @@
The <literal>rows</literal> column indicates the number of
rows MySQL believes it must examine to execute the query.
</para>
+
+ <para>
+ For <literal role="se">InnoDB</literal> tables, this number
+ is an estimate, and may not always be exact.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-5.1/information-schema.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 2, Lines Added: 15, Lines Deleted: 3; 1558 bytes
@@ -645,11 +645,16 @@
<para>
The <literal>TABLE_ROWS</literal> column is
<literal>NULL</literal> if the table is in the
- <literal>INFORMATION_SCHEMA</literal> database. For
- <literal>InnoDB</literal> tables, the row count is only a
- rough estimate used in SQL optimization.
+ <literal>INFORMATION_SCHEMA</literal> database.
</para>
+ <para>
+ For <literal role="se">InnoDB</literal> tables, the row count
+ is only a rough estimate used in SQL optimization. (This is
+ also true if the <literal role="se">InnoDB</literal> table is
+ partitioned.)
+ </para>
+
<remark role="todo">
TEMPORARY tables are missing at the moment; perhaps because
they don't appear in the output of SHOW TABLES, either?
@@ -4008,6 +4013,13 @@
<literal>TABLE_ROWS</literal>: The number of table rows in the
partition.
</para>
+
+ <para>
+ For partitioned <literal role="se">InnoDB</literal> tables,
+ the row count given in the <literal>TABLE_ROWS</literal>
+ column is only an estimated value used in SQL optimization,
+ and may not always be exact.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.1/optimization.xml
===================================================================
--- trunk/refman-5.1/optimization.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-5.1/optimization.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 642 bytes
@@ -1492,6 +1492,11 @@
The <literal>rows</literal> column indicates the number of
rows MySQL believes it must examine to execute the query.
</para>
+
+ <para>
+ For <literal role="se">InnoDB</literal> tables, this number
+ is an estimate, and may not always be exact.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.4/information-schema.xml
===================================================================
--- trunk/refman-5.4/information-schema.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-5.4/information-schema.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 2, Lines Added: 15, Lines Deleted: 3; 1558 bytes
@@ -645,11 +645,16 @@
<para>
The <literal>TABLE_ROWS</literal> column is
<literal>NULL</literal> if the table is in the
- <literal>INFORMATION_SCHEMA</literal> database. For
- <literal>InnoDB</literal> tables, the row count is only a
- rough estimate used in SQL optimization.
+ <literal>INFORMATION_SCHEMA</literal> database.
</para>
+ <para>
+ For <literal role="se">InnoDB</literal> tables, the row count
+ is only a rough estimate used in SQL optimization. (This is
+ also true if the <literal role="se">InnoDB</literal> table is
+ partitioned.)
+ </para>
+
<remark role="todo">
TEMPORARY tables are missing at the moment; perhaps because
they don't appear in the output of SHOW TABLES, either?
@@ -3993,6 +3998,13 @@
<literal>TABLE_ROWS</literal>: The number of table rows in the
partition.
</para>
+
+ <para>
+ For partitioned <literal role="se">InnoDB</literal> tables,
+ the row count given in the <literal>TABLE_ROWS</literal>
+ column is only an estimated value used in SQL optimization,
+ and may not always be exact.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-5.4/optimization.xml
===================================================================
--- trunk/refman-5.4/optimization.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-5.4/optimization.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 642 bytes
@@ -1491,6 +1491,11 @@
The <literal>rows</literal> column indicates the number of
rows MySQL believes it must examine to execute the query.
</para>
+
+ <para>
+ For <literal role="se">InnoDB</literal> tables, this number
+ is an estimate, and may not always be exact.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-6.0/information-schema.xml
===================================================================
--- trunk/refman-6.0/information-schema.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-6.0/information-schema.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 2, Lines Added: 15, Lines Deleted: 3; 1558 bytes
@@ -645,11 +645,16 @@
<para>
The <literal>TABLE_ROWS</literal> column is
<literal>NULL</literal> if the table is in the
- <literal>INFORMATION_SCHEMA</literal> database. For
- <literal>InnoDB</literal> tables, the row count is only a
- rough estimate used in SQL optimization.
+ <literal>INFORMATION_SCHEMA</literal> database.
</para>
+ <para>
+ For <literal role="se">InnoDB</literal> tables, the row count
+ is only a rough estimate used in SQL optimization. (This is
+ also true if the <literal role="se">InnoDB</literal> table is
+ partitioned.)
+ </para>
+
<remark role="todo">
TEMPORARY tables are missing at the moment; perhaps because
they don't appear in the output of SHOW TABLES, either?
@@ -4072,6 +4077,13 @@
<literal>TABLE_ROWS</literal>: The number of table rows in the
partition.
</para>
+
+ <para>
+ For partitioned <literal role="se">InnoDB</literal> tables,
+ the row count given in the <literal>TABLE_ROWS</literal>
+ column is only an estimated value used in SQL optimization,
+ and may not always be exact.
+ </para>
</listitem>
<listitem>
Modified: trunk/refman-6.0/optimization.xml
===================================================================
--- trunk/refman-6.0/optimization.xml 2009-05-30 02:47:01 UTC (rev 15131)
+++ trunk/refman-6.0/optimization.xml 2009-05-30 05:19:33 UTC (rev 15132)
Changed blocks: 1, Lines Added: 5, Lines Deleted: 0; 642 bytes
@@ -1491,6 +1491,11 @@
The <literal>rows</literal> column indicates the number of
rows MySQL believes it must examine to execute the query.
</para>
+
+ <para>
+ For <literal role="se">InnoDB</literal> tables, this number
+ is an estimate, and may not always be exact.
+ </para>
</listitem>
<listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r15132 - in trunk: refman-4.1 refman-5.0 refman-5.1 refman-5.4 refman-6.0 | jon.stephens | 30 May |
