Author: paul
Date: 2007-01-07 01:57:34 +0100 (Sun, 07 Jan 2007)
New Revision: 4389
Log:
r17651@polar: paul | 2007-01-06 18:54:25 -0600
Fix typo. (Thanks, James)
Modified:
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
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:17427
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:13874
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13015
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:17651
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:13874
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:13015
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2007-01-06 14:41:05 UTC (rev 4388)
+++ trunk/refman-4.1/sql-syntax.xml 2007-01-07 00:57:34 UTC (rev 4389)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 5; 1728 bytes
@@ -3511,7 +3511,7 @@
<para>
<literal>DELETE QUICK</literal> is not useful when deleted
- values lead to undef-filled index blocks spanning a range of
+ values lead to underfilled index blocks spanning a range of
index values for which new inserts occur again. In this case,
use of <literal>QUICK</literal> can lead to wasted space in the
index that remains unreclaimed. Here is an example of such a
@@ -3545,14 +3545,14 @@
<para>
In this scenario, the index blocks associated with the deleted
- index values become undef-filled but are not merged with other
+ index values become underfilled but are not merged with other
index blocks due to the use of <literal>QUICK</literal>. They
- remain undef-filled when new inserts occur, because new rows do
+ remain underfilled when new inserts occur, because new rows do
not have index values in the deleted range. Furthermore, they
- remain undef-filled even if you later use
+ remain underfilled 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 undef-filled blocks. To reclaim
+ blocks within or adjacent to the underfilled blocks. To reclaim
unused index space under these circumstances, use
<literal>OPTIMIZE TABLE</literal>.
</para>
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2007-01-06 14:41:05 UTC (rev 4388)
+++ trunk/refman-5.0/sql-syntax.xml 2007-01-07 00:57:34 UTC (rev 4389)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 5; 1728 bytes
@@ -3501,7 +3501,7 @@
<para>
<literal>DELETE QUICK</literal> is not useful when deleted
- values lead to undef-filled index blocks spanning a range of
+ values lead to underfilled index blocks spanning a range of
index values for which new inserts occur again. In this case,
use of <literal>QUICK</literal> can lead to wasted space in the
index that remains unreclaimed. Here is an example of such a
@@ -3535,14 +3535,14 @@
<para>
In this scenario, the index blocks associated with the deleted
- index values become undef-filled but are not merged with other
+ index values become underfilled but are not merged with other
index blocks due to the use of <literal>QUICK</literal>. They
- remain undef-filled when new inserts occur, because new rows do
+ remain underfilled when new inserts occur, because new rows do
not have index values in the deleted range. Furthermore, they
- remain undef-filled even if you later use
+ remain underfilled 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 undef-filled blocks. To reclaim
+ blocks within or adjacent to the underfilled blocks. To reclaim
unused index space under these circumstances, use
<literal>OPTIMIZE TABLE</literal>.
</para>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2007-01-06 14:41:05 UTC (rev 4388)
+++ trunk/refman-5.1/sql-syntax.xml 2007-01-07 00:57:34 UTC (rev 4389)
Changed blocks: 2, Lines Added: 5, Lines Deleted: 5; 1728 bytes
@@ -4921,7 +4921,7 @@
<para>
<literal>DELETE QUICK</literal> is not useful when deleted
- values lead to under-filled index blocks spanning a range of
+ values lead to underfilled index blocks spanning a range of
index values for which new inserts occur again. In this case,
use of <literal>QUICK</literal> can lead to wasted space in the
index that remains unreclaimed. Here is an example of such a
@@ -4955,14 +4955,14 @@
<para>
In this scenario, the index blocks associated with the deleted
- index values become under-filled but are not merged with other
+ index values become underfilled 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
+ remain underfilled 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 underfilled 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
+ blocks within or adjacent to the underfilled blocks. To reclaim
unused index space under these circumstances, use
<literal>OPTIMIZE TABLE</literal>.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4389 - in trunk: . refman-4.1 refman-5.0 refman-5.1 | paul | 7 Jan |
