Author: paul
Date: 2007-02-23 16:33:27 +0100 (Fri, 23 Feb 2007)
New Revision: 5040
Log:
r16742@frost: paul | 2007-02-23 09:19:33 -0600
Replace spatial term with logical one that is not susceptible to
page breaks.
Modified:
trunk/falcon/se-falcon.xml
trunk/internals/fileformats.xml
trunk/internals/myisam.xml
trunk/refman-4.1/replication.xml
trunk/refman-4.1/sql-syntax.xml
trunk/refman-5.0/replication.xml
trunk/refman-5.0/sql-syntax.xml
trunk/refman-5.1/replication-configuration.xml
trunk/refman-5.1/replication-solutions.xml
trunk/refman-5.1/se-falcon.xml
trunk/refman-5.1/sql-syntax.xml
trunk/refman-common/connector-mxj.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:20380
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16731
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:20380
7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:16742
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:14593
Modified: trunk/falcon/se-falcon.xml
===================================================================
--- trunk/falcon/se-falcon.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/falcon/se-falcon.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 761 bytes
@@ -212,7 +212,7 @@
Two further files contain the on-disk copy of the Falcon serial
log. These are also created within the realm of the corresponding
database. In a future release, you will be able to specify an
- alternate location for these log files. So with the above example
+ alternate location for these log files. So with the preceding example
data file <filename>test.fts</filename> the log files will be
named <filename>test.fl1</filename> and
<filename>test.fl2</filename>.
Modified: trunk/internals/fileformats.xml
===================================================================
--- trunk/internals/fileformats.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/internals/fileformats.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 826 bytes
@@ -121,7 +121,7 @@
details are correct by comparing this description with the
statements in <filename>sql/table.cc</filename>,
<literal>create_frm()</literal>. The table below explains the
- meaning of each byte in the hexadecimal dump shown in the above example.
+ meaning of each byte in the hexadecimal dump shown in the preceding example.
The Offset column shows the byte position in the file; Length is
the number of bytes; Value is what's in that byte position for
that length (remember that storage is "low byte first" so 0010
Modified: trunk/internals/myisam.xml
===================================================================
--- trunk/internals/myisam.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/internals/myisam.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 640 bytes
@@ -1631,7 +1631,7 @@
<listitem>
<para>
If a key value is <literal>NULL</literal>, then the first byte
- is 0x00 (instead of 001 as in the above examples) and that's
+ is 0x00 (instead of 001 as in the preceding examples) and that's
all. Even for a fixed <literal>CHAR(3)</literal> column, the
size of the key value is only 1 byte.
</para>
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-4.1/replication.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 657 bytes
@@ -3273,7 +3273,7 @@
<note>
<para>
- In the above example the statement is replicated because
+ In the preceding example the statement is replicated because
<option>--replicate-ignore-db</option> only applies to the
default database (set through the <literal>USE</literal>
statement). Because the <literal>sales</literal> database
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-4.1/sql-syntax.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 737 bytes
@@ -5299,7 +5299,7 @@
Note that you must run the command that generates the data to be
loaded and the <command>mysql</command> commands either on
separate terminals, or run the data generation process in the
- background (as shown in the above example). If you do not do
+ background (as shown in the preceding example). If you do not do
this, the pipe will block until data is read by the
<command>mysql</command> process.
</para>
Modified: trunk/refman-5.0/replication.xml
===================================================================
--- trunk/refman-5.0/replication.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-5.0/replication.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 657 bytes
@@ -3253,7 +3253,7 @@
<note>
<para>
- In the above example the statement is replicated because
+ In the preceding example the statement is replicated because
<option>--replicate-ignore-db</option> only applies to the
default database (set through the <literal>USE</literal>
statement). Because the <literal>sales</literal> database
Modified: trunk/refman-5.0/sql-syntax.xml
===================================================================
--- trunk/refman-5.0/sql-syntax.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-5.0/sql-syntax.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 737 bytes
@@ -5254,7 +5254,7 @@
Note that you must run the command that generates the data to be
loaded and the <command>mysql</command> commands either on
separate terminals, or run the data generation process in the
- background (as shown in the above example). If you do not do
+ background (as shown in the preceding example). If you do not do
this, the pipe will block until data is read by the
<command>mysql</command> process.
</para>
Modified: trunk/refman-5.1/replication-configuration.xml
===================================================================
--- trunk/refman-5.1/replication-configuration.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-5.1/replication-configuration.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 699 bytes
@@ -2848,7 +2848,7 @@
<note>
<para>
- In the above example the statement is replicated because
+ In the preceding example the statement is replicated because
<option>--replicate-ignore-db</option> only applies to the
default database (set through the <literal>USE</literal>
statement). Because the <literal>sales</literal> database
Modified: trunk/refman-5.1/replication-solutions.xml
===================================================================
--- trunk/refman-5.1/replication-solutions.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-5.1/replication-solutions.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 622 bytes
@@ -174,7 +174,7 @@
</orderedlist>
<para>
- In the above example you may want to add login credentials
+ In the preceding example you may want to add login credentials
(username, password) to the commands, and bundle the process up
into a script that you can run automatically each day.
</para>
Modified: trunk/refman-5.1/se-falcon.xml
===================================================================
--- trunk/refman-5.1/se-falcon.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-5.1/se-falcon.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 773 bytes
@@ -344,7 +344,7 @@
Two further files contain the on-disk copy of the Falcon serial
log. These are also created within the realm of the corresponding
database. In a future release, you will be able to specify an
- alternate location for these log files. So with the above example
+ alternate location for these log files. So with the preceding example
data file <filename>test.fts</filename> the log files will be
named <filename>test.fl1</filename> and
<filename>test.fl2</filename>.
Modified: trunk/refman-5.1/sql-syntax.xml
===================================================================
--- trunk/refman-5.1/sql-syntax.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-5.1/sql-syntax.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 737 bytes
@@ -6935,7 +6935,7 @@
Note that you must run the command that generates the data to be
loaded and the <command>mysql</command> commands either on
separate terminals, or run the data generation process in the
- background (as shown in the above example). If you do not do
+ background (as shown in the preceding example). If you do not do
this, the pipe will block until data is read by the
<command>mysql</command> process.
</para>
Modified: trunk/refman-common/connector-mxj.xml
===================================================================
--- trunk/refman-common/connector-mxj.xml 2007-02-23 13:36:20 UTC (rev 5039)
+++ trunk/refman-common/connector-mxj.xml 2007-02-23 15:33:27 UTC (rev 5040)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 734 bytes
@@ -1390,7 +1390,7 @@
<para>
The MySQL version directory, <literal>5-0-22</literal> or
- <literal>5-0-27</literal> in the above examples, contains all of
+ <literal>5-0-27</literal> in the preceding examples, contains all of
the files used to create an instance of MySQL when Connector/MXJ
is executed. All of the files in this directory are required for
each version of MySQL that you want to embed. Note as well the
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5040 - in trunk: . falcon internals refman-4.1 refman-5.0 refman-5.1 refman-common | paul | 23 Feb |
