Author: jstephens
Date: 2006-04-03 15:08:55 +0200 (Mon, 03 Apr 2006)
New Revision: 1718
Log:
Fixed some typos/garbled wording in ansi-diff-comments I noticed whilst deleting
comments.
(Gigan Lives!)
Modified:
trunk/refman-4.1/introduction.xml
trunk/refman-5.0/introduction.xml
trunk/refman-5.1/introduction.xml
Modified: trunk/refman-4.1/introduction.xml
===================================================================
--- trunk/refman-4.1/introduction.xml 2006-04-02 06:55:00 UTC (rev 1717)
+++ trunk/refman-4.1/introduction.xml 2006-04-03 13:08:55 UTC (rev 1718)
@@ -2674,11 +2674,11 @@
problems with automatically generated SQL queries that use
constructs such as the following, where we automatically
insert the value of the payment for
- <literal>!payment!</literal>:
+ <literal>payment</literal>:
</para>
<programlisting>
-UPDATE account SET credit=credit-!payment!
+UPDATE account SET credit=credit-payment
</programlisting>
<para>
@@ -2703,17 +2703,18 @@
</programlisting>
<para>
- The statement produces no change in value at all! This
+ The statement produces no change in value at all. This
illustrates that allowing comments to start with
‘<literal>--</literal>’ can have serious
consequences.
</para>
<para>
- Using our implementation of require a following space for
- ‘<literal>--</literal>’ to be recognized as a
- start-comment sequence in MySQL Server 3.23.3 and up,
- <literal>credit--1</literal> is actually safe.
+ Using our implementation requires a space following the
+ ‘<literal>--</literal>’ in order for it to be
+ recognized as a start-comment sequence in MySQL Server 3.23.3
+ and newer. Therefore, <literal>credit--1</literal> is safe to
+ use.
</para>
<para>
Modified: trunk/refman-5.0/introduction.xml
===================================================================
--- trunk/refman-5.0/introduction.xml 2006-04-02 06:55:00 UTC (rev 1717)
+++ trunk/refman-5.0/introduction.xml 2006-04-03 13:08:55 UTC (rev 1718)
@@ -2322,11 +2322,11 @@
problems with automatically generated SQL queries that use
constructs such as the following, where we automatically
insert the value of the payment for
- <literal>!payment!</literal>:
+ <literal>payment</literal>:
</para>
<programlisting>
-UPDATE account SET credit=credit-!payment!
+UPDATE account SET credit=credit-payment
</programlisting>
<para>
@@ -2351,17 +2351,18 @@
</programlisting>
<para>
- The statement produces no change in value at all! This
+ The statement produces no change in value at all. This
illustrates that allowing comments to start with
‘<literal>--</literal>’ can have serious
consequences.
</para>
<para>
- Using our implementation of require a following space for
- ‘<literal>--</literal>’ to be recognized as a
- start-comment sequence in MySQL Server 3.23.3 and up,
- <literal>credit--1</literal> is actually safe.
+ Using our implementation requires a space following the
+ ‘<literal>--</literal>’ in order for it to be
+ recognized as a start-comment sequence in MySQL Server 3.23.3
+ and newer. Therefore, <literal>credit--1</literal> is safe to
+ use.
</para>
<para>
Modified: trunk/refman-5.1/introduction.xml
===================================================================
--- trunk/refman-5.1/introduction.xml 2006-04-02 06:55:00 UTC (rev 1717)
+++ trunk/refman-5.1/introduction.xml 2006-04-03 13:08:55 UTC (rev 1718)
@@ -2315,11 +2315,11 @@
problems with automatically generated SQL queries that use
constructs such as the following, where we automatically
insert the value of the payment for
- <literal>!payment!</literal>:
+ <literal>payment</literal>:
</para>
<programlisting>
-UPDATE account SET credit=credit-!payment!
+UPDATE account SET credit=credit-payment
</programlisting>
<para>
@@ -2344,17 +2344,18 @@
</programlisting>
<para>
- The statement produces no change in value at all! This
+ The statement produces no change in value at all. This
illustrates that allowing comments to start with
‘<literal>--</literal>’ can have serious
consequences.
</para>
<para>
- Using our implementation of require a following space for
- ‘<literal>--</literal>’ to be recognized as a
- start-comment sequence in MySQL Server 3.23.3 and up,
- <literal>credit--1</literal> is actually safe.
+ Using our implementation requires a space following the
+ ‘<literal>--</literal>’ in order for it to be
+ recognized as a start-comment sequence in MySQL Server 3.23.3
+ and newer. Therefore, <literal>credit--1</literal> is safe to
+ use.
</para>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1718 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 3 Apr |
