Author: paul
Date: 2006-03-16 01:00:45 +0100 (Thu, 16 Mar 2006)
New Revision: 1595
Log:
r8711@frost: paul | 2006-03-15 17:41:56 -0600
SHOW TABLE STATUS shows NULL for Update_time for InnoDB.
(Bug##15438, Bug#18229)
Modified:
trunk/
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/sql-syntax.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8707
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3931
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8711
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:3931
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2006-03-15 20:33:20 UTC (rev 1594)
+++ trunk/refman-4.1/sql-syntax.xml 2006-03-16 00:00:45 UTC (rev 1595)
@@ -15810,7 +15810,11 @@
</para>
<para>
- When the data file was last updated.
+ When the data file was last updated. For some storage
+ engines, this value is <literal>NULL</literal>. For
+ example, <literal>InnoDB</literal> stores multiple tables
+ in its tablespace and the data file timestamp does not
+ apply.
</para>
</listitem>
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2006-03-15 20:33:20 UTC (rev 1594)
+++ trunk/refman-5.0/sql-syntax.xml 2006-03-16 00:00:45 UTC (rev 1595)
@@ -17300,7 +17300,11 @@
</para>
<para>
- When the data file was last updated.
+ When the data file was last updated. For some storage
+ engines, this value is <literal>NULL</literal>. For
+ example, <literal>InnoDB</literal> stores multiple tables
+ in its tablespace and the data file timestamp does not
+ apply.
</para>
</listitem>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-03-15 20:33:20 UTC (rev 1594)
+++ trunk/refman-5.1/sql-syntax.xml 2006-03-16 00:00:45 UTC (rev 1595)
@@ -3589,10 +3589,10 @@
LOGFILE GROUP</literal> statement has one and only one
<literal>ADD UNDOFILE</literal> clause.
</para>
-
+
<para>
- Beginning with MySQL 5.1.8, you can have only one logfile group per
- Cluster at any given time. (See Bug #16386)
+ Beginning with MySQL 5.1.8, you can have only one logfile group
+ per Cluster at any given time. (See Bug #16386)
</para>
<para>
@@ -3600,16 +3600,16 @@
<literal>UNDO</literal> file's initial size. The optional
<literal>UNDO_BUFFFER_SIZE</literal> parameter sets the size
used by the <literal>UNDO</literal> buffer for the logfile
- group; The default value for <literal>UNDO_BUFFER_SIZE</literal> is
- <literal>8M</literal> (eight megabytes); this value cannot exceeed the
- amount of system memory avilable. Both
+ group; The default value for <literal>UNDO_BUFFER_SIZE</literal>
+ is <literal>8M</literal> (eight megabytes); this value cannot
+ exceeed the amount of system memory avilable. Both
<replaceable>initial_size</replaceable> and
- <replaceable>undo_buffer_size_size</replaceable> are specified in bytes.
- You may optionally follow either or both of these with a one-letter
- abbreviation for an order of magnitude, similar to those used in
- <filename>my.cnf</filename>. Generally, this is one of the letters
- <literal>M</literal> (for megabytes) or <literal>G</literal> (for
- gigabytes).
+ <replaceable>undo_buffer_size_size</replaceable> are specified
+ in bytes. You may optionally follow either or both of these with
+ a one-letter abbreviation for an order of magnitude, similar to
+ those used in <filename>my.cnf</filename>. Generally, this
+ is one of the letters <literal>M</literal> (for megabytes) or
+ <literal>G</literal> (for gigabytes).
</para>
<para>
@@ -4543,9 +4543,9 @@
In this scenario, the index blocks associated with the deleted
index values become under-filled but are not merged with other
index blocks due to the use of <literal>QUICK</literal>. They
- remain under-filled when new inserts occur, because new rows
- do not have index values in the deleted range. Furthermore,
- they remain under-filled even if you later use
+ remain under-filled when new inserts occur, because new rows do
+ not have index values in the deleted range. Furthermore, they
+ remain under-filled even if you later use
<literal>DELETE</literal> without <literal>QUICK</literal>,
unless some of the deleted index values happen to lie in index
blocks within or adjacent to the under-filled blocks. To reclaim
@@ -18654,7 +18654,11 @@
</para>
<para>
- When the data file was last updated.
+ When the data file was last updated. For some storage
+ engines, this value is <literal>NULL</literal>. For
+ example, <literal>InnoDB</literal> stores multiple tables
+ in its tablespace and the data file timestamp does not
+ apply.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1595 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 16 Mar |
