Author: jstephens
Date: 2006-03-08 11:08:45 +0100 (Wed, 08 Mar 2006)
New Revision: 1528
Log:
Spellcheck; replace >s with >s.
Modified:
trunk/refman-5.1/information-schema.xml
trunk/refman-5.1/ndbcluster.xml
trunk/refman-5.1/sql-syntax.xml
Modified: trunk/refman-5.1/information-schema.xml
===================================================================
--- trunk/refman-5.1/information-schema.xml 2006-03-08 09:15:40 UTC (rev 1527)
+++ trunk/refman-5.1/information-schema.xml 2006-03-08 10:08:45 UTC (rev 1528)
@@ -4411,7 +4411,7 @@
<listitem>
<para>
- For MySQL 5.1 CLuster Disk Data files, the following columns
+ For MySQL 5.1 Cluster Disk Data files, the following columns
are always <literal>NULL</literal>:
</para>
Modified: trunk/refman-5.1/ndbcluster.xml
===================================================================
--- trunk/refman-5.1/ndbcluster.xml 2006-03-08 09:15:40 UTC (rev 1527)
+++ trunk/refman-5.1/ndbcluster.xml 2006-03-08 10:08:45 UTC (rev 1528)
@@ -10231,7 +10231,7 @@
belonging to these columns is stored in RAM. In MySQL 5.1,
only non-indexed columns can be held on disk; indexes and
indexed column data continue to be stored in memory. This
- tradeoff between the use of indexes and conservation of RAM is
+ trade-off between the use of indexes and conservation of RAM is
something you must keep in mind as you design Disk Data
tables.
</para>
@@ -10276,17 +10276,21 @@
</para>
<programlisting>
-mysql> <userinput>DROP TABLE dt_1;</userinput>
-mysql> <userinput>ALTER TABLESPACE ts_1</userinput>
- -> <userinput>DROP DATAFILE 'data_2.dat'</userinput>
- -> <userinput>ENGINE NDB;</userinput>
-mysql> <userinput>ALTER TABLESPACE ts_1</userinput>
- -> <userinput>DROP DATAFILE 'data_1.dat'</userinput>
- -> <userinput>ENGINE NDB;</userinput>
-mysql> <userinput>DROP TABLESPACE ts_1</userinput>
- -> <userinput>ENGINE NDB;</userinput>
-mysql> <userinput>DROP LOGFILE GROUP lg_1</userinput>
- -> <userinput>ENGINE NDB;</userinput>
+mysql> <userinput>DROP TABLE dt_1;</userinput>
+
+mysql> <userinput>ALTER TABLESPACE ts_1</userinput>
+ -> <userinput>DROP DATAFILE 'data_2.dat'</userinput>
+ -> <userinput>ENGINE NDB;</userinput>
+
+mysql> <userinput>ALTER TABLESPACE ts_1</userinput>
+ -> <userinput>DROP DATAFILE 'data_1.dat'</userinput>
+ -> <userinput>ENGINE NDB;</userinput>
+
+mysql> <userinput>DROP TABLESPACE ts_1</userinput>
+ -> <userinput>ENGINE NDB;</userinput>
+
+mysql> <userinput>DROP LOGFILE GROUP lg_1</userinput>
+ -> <userinput>ENGINE NDB;</userinput>
</programlisting>
<para>
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2006-03-08 09:15:40 UTC (rev 1527)
+++ trunk/refman-5.1/sql-syntax.xml 2006-03-08 10:08:45 UTC (rev 1528)
@@ -845,7 +845,7 @@
<para>
<emphasis role="bold">Note</emphasis>: You cannot use
<literal>ALTER TABLE</literal> to add partitions to a table
- that is not not already partitioned.
+ that is not already partitioned.
</para>
<para>
@@ -2545,7 +2545,7 @@
<para>
<emphasis role="bold">Note</emphasis>: The older
- <literal>TYPE</literal> option was synomous with
+ <literal>TYPE</literal> option was synonymous with
<literal>ENGINE</literal>. <literal>TYPE</literal> has been
deprecated since MySQL 4.0 but is still supported for backwards
compatibility in MySQL 5.1 (excepting MySQL 5.1.7). Since MySQL
@@ -3346,9 +3346,9 @@
option for both <literal>PARTITION</literal> and
<literal>SUBPARTITION</literal>. Currently, the only way
in which this can be used is to set all partitions or
- all subpartitions to the same sorage engine, and an
+ all subpartitions to the same storage engine, and an
attempt to set different storage engines for partitions
- or ubpartitions in the same table will give rise to the
+ or subpartitions in the same table will give rise to the
error <literal>ERROR 1469 (HY000): The mix of handlers
in the partitions is not allowed in this version of
MySQL</literal>. We expect to lift this restriction on
@@ -4494,7 +4494,7 @@
<para>
<literal>DELETE QUICK</literal> is not useful when deleted
- values lead to underfilled index blocks spanning a range of
+ values lead to under-filled 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
@@ -4528,14 +4528,14 @@
<para>
In this scenario, the index blocks associated with the deleted
- index values become underfilled but are not merged with other
+ index values become under-filled but are not merged with other
index blocks due to the use of <literal>QUICK</literal>. They
- remain underfilled when new inserts occur, because new rows does
+ remain under-filled when new inserts occur, because new rows does
not have index values in the deleted range. Furthermore, they
- remain underfilled even if you later use
+ 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 underfilled blocks. To reclaim
+ blocks within or adjacent to the under-filled blocks. To reclaim
unused index space under these circumstances, use
<literal>OPTIMIZE TABLE</literal>.
</para>
@@ -10272,7 +10272,7 @@
</programlisting>
<para>
- Can be be rewritten using <literal>IN()</literal>:
+ Can be rewritten using <literal>IN()</literal>:
</para>
<programlisting>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1528 - trunk/refman-5.1 | jon | 8 Mar |
