Author: jstephens
Date: 2007-10-08 11:42:49 +0200 (Mon, 08 Oct 2007)
New Revision: 8012
Log:
‘ ... ’ -> <quote>...</quote> (4.1)
Modified:
trunk/refman-4.1/apis-c.xml
trunk/refman-4.1/apis.xml
trunk/refman-4.1/charset.xml
trunk/refman-4.1/client-utility-programs.xml
trunk/refman-4.1/data-types.xml
trunk/refman-4.1/dba-core.xml
trunk/refman-4.1/errors-problems.xml
trunk/refman-4.1/functions-core.xml
trunk/refman-4.1/installing.xml
trunk/refman-4.1/introduction.xml
trunk/refman-4.1/language-structure.xml
trunk/refman-4.1/mysql-cluster-configuration.xml
trunk/refman-4.1/news-3.22.xml
trunk/refman-4.1/news-3.23.xml
trunk/refman-4.1/news-4.0.xml
trunk/refman-4.1/news-4.1.xml
trunk/refman-4.1/optimization.xml
trunk/refman-4.1/replication.xml
trunk/refman-4.1/se-innodb.xml
trunk/refman-4.1/sql-syntax.xml
trunk/refman-4.1/tutorial.xml
trunk/refman-4.1/using-mysql-programs.xml
Modified: trunk/refman-4.1/apis-c.xml
===================================================================
--- trunk/refman-4.1/apis-c.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/apis-c.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 13, Lines Added: 21, Lines Deleted: 21; 7686 bytes
@@ -4214,8 +4214,8 @@
that match the simple regular expression specified by the
<literal>wild</literal> parameter. <literal>wild</literal> may
contain the wildcard characters
- ‘<literal>%</literal>’ or
- ‘<literal>_</literal>’, or may be a
+ <quote><literal>%</literal></quote> or
+ <quote><literal>_</literal></quote>, or may be a
<literal>NULL</literal> pointer to match all databases. Calling
<literal>mysql_list_dbs()</literal> is similar to executing the
query <literal>SHOW databases [LIKE
@@ -4318,8 +4318,8 @@
table that match the simple regular expression specified by the
<replaceable>wild</replaceable> parameter.
<replaceable>wild</replaceable> may contain the wildcard
- characters ‘<literal>%</literal>’ or
- ‘<literal>_</literal>’, or may be a
+ characters <quote><literal>%</literal></quote> or
+ <quote><literal>_</literal></quote>, or may be a
<literal>NULL</literal> pointer to match all fields. Calling
<literal>mysql_list_fields()</literal> is similar to executing
the query <literal>SHOW COLUMNS FROM
@@ -4506,8 +4506,8 @@
database that match the simple regular expression specified by
the <literal>wild</literal> parameter. <literal>wild</literal>
may contain the wildcard characters
- ‘<literal>%</literal>’ or
- ‘<literal>_</literal>’, or may be a
+ <quote><literal>%</literal></quote> or
+ <quote><literal>_</literal></quote>, or may be a
<literal>NULL</literal> pointer to match all tables. Calling
<literal>mysql_list_tables()</literal> is similar to executing
the query <literal>SHOW tables [LIKE
@@ -5364,7 +5364,7 @@
<row>
<entry><literal>multi-statements</literal></entry>
<entry>Allow the client to send multiple statements in a single string
- (separated by ‘<literal>;</literal>’). Added
+ (separated by <quote><literal>;</literal></quote>). Added
in 4.1.9.</entry>
</row>
<row>
@@ -5551,7 +5551,7 @@
Executes the SQL statement pointed to by the null-terminated
string <literal>stmt_str</literal>. Normally, the string must
consist of a single SQL statement and you should not add a
- terminating semicolon (‘<literal>;</literal>’) or
+ terminating semicolon (<quote><literal>;</literal></quote>) or
<literal>\g</literal> to the statement. If multiple-statement
execution has been enabled, the string can contain several
statements separated by semicolons. See
@@ -5562,7 +5562,7 @@
<literal>mysql_query()</literal> cannot be used for statements
that contain binary data; you must use
<literal>mysql_real_query()</literal> instead. (Binary data may
- contain the ‘<literal>\0</literal>’ character, which
+ contain the <quote><literal>\0</literal></quote> character, which
<literal>mysql_query()</literal> interprets as the end of the
statement string.)
</para>
@@ -5828,7 +5828,7 @@
<entry><literal>CLIENT_MULTI_STATEMENTS</literal></entry>
<entry>Tell the server that the client may send multiple statements in a single
string (separated by
- ‘<literal>;</literal>’). If this flag is
+ <quote><literal>;</literal></quote>). If this flag is
not set, multiple-statement execution is disabled.
See the note following this table for more
information about this flag. Added in MySQL 4.1.</entry>
@@ -6146,11 +6146,11 @@
connection. The result is placed in <literal>to</literal> and a
terminating null byte is appended. Characters encoded are
<literal>NUL</literal> (ASCII 0),
- ‘<literal>\n</literal>’,
- ‘<literal>\r</literal>’,
- ‘<literal>\</literal>’,
- ‘<literal>'</literal>’,
- ‘<literal>"</literal>’, and Control-Z (see
+ <quote><literal>\n</literal></quote>,
+ <quote><literal>\r</literal></quote>,
+ <quote><literal>\</literal></quote>,
+ <quote><literal>'</literal></quote>,
+ <quote><literal>"</literal></quote>, and Control-Z (see
<xref linkend="literals"/>). (Strictly speaking, MySQL requires
only that backslash and the quote character used to quote the
string in the query be escaped. This function quotes the other
@@ -6253,7 +6253,7 @@
<literal>stmt_str</literal>, which should be a string
<literal>length</literal> bytes long. Normally, the string must
consist of a single SQL statement and you should not add a
- terminating semicolon (‘<literal>;</literal>’) or
+ terminating semicolon (<quote><literal>;</literal></quote>) or
<literal>\g</literal> to the statement. If multiple-statement
execution has been enabled, the string can contain several
statements separated by semicolons. See
@@ -6264,7 +6264,7 @@
<literal>mysql_query()</literal> cannot be used for statements
that contain binary data; you must use
<literal>mysql_real_query()</literal> instead. (Binary data may
- contain the ‘<literal>\0</literal>’ character, which
+ contain the <quote><literal>\0</literal></quote> character, which
<literal>mysql_query()</literal> interprets as the end of the
statement string.) In addition,
<literal>mysql_real_query()</literal> is faster than
@@ -9682,7 +9682,7 @@
<literal>bind</literal> is the address of an array of
<literal>MYSQL_BIND</literal> structures. The client library
expects the array to contain one element for each
- ‘<literal>?</literal>’ parameter marker that is
+ <quote><literal>?</literal></quote> parameter marker that is
present in the query.
</para>
@@ -11434,14 +11434,14 @@
a status value. The string length should be given by the
<literal>length</literal> argument. The string must consist of a
single SQL statement. You should not add a terminating semicolon
- (‘<literal>;</literal>’) or <literal>\g</literal> to
+ (<quote><literal>;</literal></quote>) or <literal>\g</literal> to
the statement.
</para>
<para>
The application can include one or more parameter markers in the
SQL statement by embedding question mark
- (‘<literal>?</literal>’) characters into the SQL
+ (<quote><literal>?</literal></quote>) characters into the SQL
string at the appropriate positions.
</para>
@@ -12358,7 +12358,7 @@
<para>
MySQL ¤t-series; also supports the execution of a string
containing multiple statements separated by semicolon
- (‘<literal>;</literal>’) characters. This capability
+ (<quote><literal>;</literal></quote>) characters. This capability
is enabled by special options that are specified either when you
connect to the server with <literal>mysql_real_connect()</literal>
or after connecting by calling`
Modified: trunk/refman-4.1/apis.xml
===================================================================
--- trunk/refman-4.1/apis.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/apis.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 651 bytes
@@ -1381,7 +1381,7 @@
<para>
When you use <command>mysql_config</command> this way, be
sure to invoke it within backtick
- (‘<literal>`</literal>’) characters. That tells
+ (<quote><literal>`</literal></quote>) characters. That tells
the shell to execute it and substitute its output into the
surrounding command.
</para>
Modified: trunk/refman-4.1/charset.xml
===================================================================
--- trunk/refman-4.1/charset.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/charset.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 8, Lines Added: 48, Lines Deleted: 48; 9354 bytes
@@ -129,29 +129,29 @@
<para>
Suppose that we have an alphabet with four letters:
- ‘<literal>A</literal>’,
- ‘<literal>B</literal>’,
- ‘<literal>a</literal>’,
- ‘<literal>b</literal>’. We give each letter a number:
- ‘<literal>A</literal>’ = 0,
- ‘<literal>B</literal>’ = 1,
- ‘<literal>a</literal>’ = 2,
- ‘<literal>b</literal>’ = 3. The letter
- ‘<literal>A</literal>’ is a symbol, the number 0 is
+ <quote><literal>A</literal></quote>,
+ <quote><literal>B</literal></quote>,
+ <quote><literal>a</literal></quote>,
+ <quote><literal>b</literal></quote>. We give each letter a number:
+ <quote><literal>A</literal></quote> = 0,
+ <quote><literal>B</literal></quote> = 1,
+ <quote><literal>a</literal></quote> = 2,
+ <quote><literal>b</literal></quote> = 3. The letter
+ <quote><literal>A</literal></quote> is a symbol, the number 0 is
the <emphasis role="bold">encoding</emphasis> for
- ‘<literal>A</literal>’, and the combination of all
+ <quote><literal>A</literal></quote>, and the combination of all
four letters and their encodings is a
<emphasis role="bold">character set</emphasis>.
</para>
<para>
Suppose that we want to compare two string values,
- ‘<literal>A</literal>’ and
- ‘<literal>B</literal>’. The simplest way to do this is
- to look at the encodings: 0 for ‘<literal>A</literal>’
- and 1 for ‘<literal>B</literal>’. Because 0 is less
- than 1, we say ‘<literal>A</literal>’ is less than
- ‘<literal>B</literal>’. What we've just done is apply
+ <quote><literal>A</literal></quote> and
+ <quote><literal>B</literal></quote>. The simplest way to do this is
+ to look at the encodings: 0 for <quote><literal>A</literal></quote>
+ and 1 for <quote><literal>B</literal></quote>. Because 0 is less
+ than 1, we say <quote><literal>A</literal></quote> is less than
+ <quote><literal>B</literal></quote>. What we've just done is apply
a collation to our character set. The collation is a set of rules
(only one rule in this case): <quote>compare the
encodings.</quote> We call this simplest of all possible
@@ -161,28 +161,28 @@
<para>
But what if we want to say that the lowercase and uppercase
letters are equivalent? Then we would have at least two rules: (1)
- treat the lowercase letters ‘<literal>a</literal>’ and
- ‘<literal>b</literal>’ as equivalent to
- ‘<literal>A</literal>’ and
- ‘<literal>B</literal>’; (2) then compare the
+ treat the lowercase letters <quote><literal>a</literal></quote> and
+ <quote><literal>b</literal></quote> as equivalent to
+ <quote><literal>A</literal></quote> and
+ <quote><literal>B</literal></quote>; (2) then compare the
encodings. We call this a <firstterm>case-insensitive</firstterm>
collation. It's a little more complex than a binary collation.
</para>
<para>
In real life, most character sets have many characters: not just
- ‘<literal>A</literal>’ and
- ‘<literal>B</literal>’ but whole alphabets, sometimes
+ <quote><literal>A</literal></quote> and
+ <quote><literal>B</literal></quote> but whole alphabets, sometimes
multiple alphabets or eastern writing systems with thousands of
characters, along with many special symbols and punctuation marks.
Also in real life, most collations have many rules, not just for
whether to distinguish lettercase, but also for whether to
distinguish accents (an <quote>accent</quote> is a mark attached
to a character as in German
- <squo;<literal>Ö</literal>’), and for multiple-character
+ <quote><literal>Ö</literal></quote>), and for multiple-character
mappings (such as the rule that
- ‘<literal>Ö</literal>’ =
- ‘<literal>OE</literal>’ in one of the two German
+ <quote><literal>Ö</literal></quote> =
+ <quote><literal>OE</literal></quote> in one of the two German
collations).
</para>
@@ -941,9 +941,9 @@
</programlisting>
<para>
- Here, ‘<literal>à</literal>’ (hex value
+ Here, <quote><literal>à</literal></quote> (hex value
<literal>E0</literal>) is followed by
- ‘<literal>\n</literal>’, the escape sequence for
+ <quote><literal>\n</literal></quote>, the escape sequence for
newline. The escape sequence is interpreted using the
<literal>character_set_connection</literal> value of
<literal>latin1</literal> to produce a literal newline (hex
@@ -972,14 +972,14 @@
<para>
Here, <literal>character_set_connection</literal> is
<literal>sjis</literal>, a character set in which the sequence
- of ‘<literal>à</literal>’ followed by
- ‘<literal>\</literal>’ (hex values
+ of <quote><literal>à</literal></quote> followed by
+ <quote><literal>\</literal></quote> (hex values
<literal>05</literal> and <literal>5C</literal>) is a valid
multi-byte character. Hence, the first two bytes of the string
are interpreted as a single <literal>sjis</literal> character,
- and the ‘<literal>\</literal>’ is not intrepreted as
+ and the <quote><literal>\</literal></quote> is not intrepreted as
an escape character. The following
- ‘<literal>n</literal>’ (hex value
+ <quote><literal>n</literal></quote> (hex value
<literal>6E</literal>) is not interpreted as part of an escape
sequence. This is true even for the second string; the
introducer of <literal>_latin1</literal> does not affect escape
@@ -3555,8 +3555,8 @@
<literal>utf8_unicode_ci</literal> is that it supports
expansions; that is, when one character compares as equal to
combinations of other characters. For example, in German and
- some other languages ‘<literal>ß</literal>’ is
- equal to ‘<literal>ss</literal>’.
+ some other languages <quote><literal>ß</literal></quote> is
+ equal to <quote><literal>ss</literal></quote>.
</para>
<para>
@@ -3624,9 +3624,9 @@
<para>
<literal>utf8_general_ci</literal> also is satisfactory for both
German and French, except that
- ‘<literal>ß</literal>’ is equal to
- ‘<literal>s</literal>’, and not to
- ‘<literal>ss</literal>’. If this is acceptable for
+ <quote><literal>ß</literal></quote> is equal to
+ <quote><literal>s</literal></quote>, and not to
+ <quote><literal>ss</literal></quote>. If this is acceptable for
your application, then you should use
<literal>utf8_general_ci</literal> because it is faster.
Otherwise, use <literal>utf8_unicode_ci</literal> because it is
@@ -3650,15 +3650,15 @@
The <literal>utf8_spanish_ci</literal> and
<literal>utf8_spanish2_ci</literal> collations correspond to
modern Spanish and traditional Spanish, respectively. In both
- collations, ‘<literal>ñ</literal>’ (n-tilde) is a
- separate letter between ‘<literal>n</literal>’ and
- ‘<literal>o</literal>’. In addition, for traditional
- Spanish, ‘<literal>ch</literal>’ is a separate
- letter between ‘<literal>c</literal>’ and
- ‘<literal>d</literal>’, and
- ‘<literal>ll</literal>’ is a separate letter between
- ‘<literal>l</literal>’ and
- ‘<literal>m</literal>’
+ collations, <quote><literal>ñ</literal></quote> (n-tilde) is a
+ separate letter between <quote><literal>n</literal></quote> and
+ <quote><literal>o</literal></quote>. In addition, for traditional
+ Spanish, <quote><literal>ch</literal></quote> is a separate
+ letter between <quote><literal>c</literal></quote> and
+ <quote><literal>d</literal></quote>, and
+ <quote><literal>ll</literal></quote> is a separate letter between
+ <quote><literal>l</literal></quote> and
+ <quote><literal>m</literal></quote>
</para>
</section>
@@ -3911,9 +3911,9 @@
<para>
In the <literal>latin1_spanish_ci</literal> collation,
- ‘<literal>ñ</literal>’ (n-tilde) is a separate
- letter between ‘<literal>n</literal>’ and
- ‘<literal>o</literal>’.
+ <quote><literal>ñ</literal></quote> (n-tilde) is a separate
+ letter between <quote><literal>n</literal></quote> and
+ <quote><literal>o</literal></quote>.
</para>
</listitem>
Modified: trunk/refman-4.1/client-utility-programs.xml
===================================================================
--- trunk/refman-4.1/client-utility-programs.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/client-utility-programs.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 11, Lines Added: 23, Lines Deleted: 23; 6444 bytes
@@ -2422,8 +2422,8 @@
directory paths that are used successively in round-robin
fashion for creating temporary files. The separator
character between directory names should be colon
- (‘<literal>:</literal>’) on Unix and semicolon
- (‘<literal>;</literal>’) on Windows, NetWare,
+ (<quote><literal>:</literal></quote>) on Unix and semicolon
+ (<quote><literal>;</literal></quote>) on Windows, NetWare,
and OS/2.
</para>
</listitem>
@@ -4037,7 +4037,7 @@
<para>
Then type an SQL statement, end it with
- ‘<literal>;</literal>’, <literal>\g</literal>, or
+ <quote><literal>;</literal></quote>, <literal>\g</literal>, or
<literal>\G</literal> and press Enter.
</para>
@@ -4317,7 +4317,7 @@
<para>
Set the statement delimiter. The default is the semicolon
- character (‘<literal>;</literal>’).
+ character (<quote><literal>;</literal></quote>).
</para>
</listitem>
@@ -4574,7 +4574,7 @@
Disable named commands. Use the <literal>\*</literal> form
only, or use named commands only at the beginning of a
line ending with a semicolon
- (‘<literal>;</literal>’). As of MySQL 3.23.22,
+ (<quote><literal>;</literal></quote>). As of MySQL 3.23.22,
<command>mysql</command> starts with this option
<emphasis>enabled</emphasis> by default. However, even
with this option, long-format commands still work from the
@@ -5488,7 +5488,7 @@
<para>
In the <literal>delimiter</literal> command, you should avoid
- the use of the backslash (‘<literal>\</literal>’)
+ the use of the backslash (<quote><literal>\</literal></quote>)
character because that is the escape character for MySQL.
</para>
@@ -5689,7 +5689,7 @@
</row>
<row>
<entry><literal>\\</literal></entry>
- <entry>A literal ‘<literal>\</literal>’ backslash character</entry>
+ <entry>A literal <quote><literal>\</literal></quote> backslash character</entry>
</row>
<row>
<entry><literal>\n</literal></entry>
@@ -5772,7 +5772,7 @@
</informaltable>
<para>
- ‘<literal>\</literal>’ followed by any other
+ <quote><literal>\</literal></quote> followed by any other
letter just becomes that letter.
</para>
@@ -11084,9 +11084,9 @@
<para>
Quote database, table, and column names within
- ‘<literal>`</literal>’ characters. If the
+ <quote><literal>`</literal></quote> characters. If the
<literal>ANSI_QUOTES</literal> SQL mode is enabled, names
- are quoted within ‘<literal>"</literal>’
+ are quoted within <quote><literal>"</literal></quote>
characters. As of MySQL 4.1.1,
<option>--quote-names</option> is enabled by default. It
can be disabled with <option>--skip-quote-names</option>,
@@ -11115,8 +11115,8 @@
<para>
Direct output to a given file. This option should be used
on Windows to prevent newline
- ‘<literal>\n</literal>’ characters from being
- converted to ‘<literal>\r\n</literal>’
+ <quote><literal>\n</literal></quote> characters from being
+ converted to <quote><literal>\r\n</literal></quote>
carriage return/newline sequences. The result file is
created and its contents overwritten, even if an error
occurs while generating the dump. The previous contents
@@ -11782,7 +11782,7 @@
<para>
The regular expression for the table name can be negated by
prefixing it with a tilde
- (‘<literal>~</literal>’):
+ (<quote><literal>~</literal></quote>):
</para>
<programlisting>
@@ -13314,23 +13314,23 @@
<para>
If the last argument contains shell or SQL wildcard characters
- (‘<literal>*</literal>’,
- ‘<literal>?</literal>’,
- ‘<literal>%</literal>’, or
- ‘<literal>_</literal>’), only those names that are
+ (<quote><literal>*</literal></quote>,
+ <quote><literal>?</literal></quote>,
+ <quote><literal>%</literal></quote>, or
+ <quote><literal>_</literal></quote>), only those names that are
matched by the wildcard are shown. If a database name contains
any underscores, those should be escaped with a backslash
(some Unix shells require two) to get a list of the proper
- tables or columns. ‘<literal>*</literal>’ and
- ‘<literal>?</literal>’ characters are converted
- into SQL ‘<literal>%</literal>’ and
- ‘<literal>_</literal>’ wildcard characters. This
+ tables or columns. <quote><literal>*</literal></quote> and
+ <quote><literal>?</literal></quote> characters are converted
+ into SQL <quote><literal>%</literal></quote> and
+ <quote><literal>_</literal></quote> wildcard characters. This
might cause some confusion when you try to display the columns
- for a table with a ‘<literal>_</literal>’ in the
+ for a table with a <quote><literal>_</literal></quote> in the
name, because in this case, <command>mysqlshow</command> shows
you only the table names that match the pattern. This is
easily fixed by adding an extra
- ‘<literal>%</literal>’ last on the command line as
+ <quote><literal>%</literal></quote> last on the command line as
a separate argument.
</para>
Modified: trunk/refman-4.1/data-types.xml
===================================================================
--- trunk/refman-4.1/data-types.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/data-types.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 5, Lines Added: 6, Lines Deleted: 6; 2642 bytes
@@ -111,8 +111,8 @@
<primary>square brackets</primary>
</indexterm>
- Square brackets (‘<literal>[</literal>’ and
- ‘<literal>]</literal>’) indicate optional parts of
+ Square brackets (<quote><literal>[</literal></quote> and
+ <quote><literal>]</literal></quote>) indicate optional parts of
type definitions.
</para>
</listitem>
@@ -864,7 +864,7 @@
the total number of digits and <replaceable>D</replaceable>
is the number of digits after the decimal point. The decimal
point and (for negative numbers) the
- ‘<literal>-</literal>’ sign are not counted in
+ <quote><literal>-</literal></quote> sign are not counted in
<replaceable>M</replaceable>, although space for them is
reserved. If <replaceable>D</replaceable> is 0, values have
no decimal point or fractional part. The maximum range of
@@ -2362,7 +2362,7 @@
<literal>NUMERIC</literal> values as strings, rather than in
binary format. One character is used for each digit of the value,
the decimal point (if the scale is greater than 0), and the
- ‘<literal>-</literal>’ sign (for negative numbers).
+ <quote><literal>-</literal></quote> sign (for negative numbers).
</para>
<para>
@@ -3005,7 +3005,7 @@
The relaxed format allowed for values specified as strings
can be deceiving. For example, a value such as
<literal>'10:11:12'</literal> might look like a time value
- because of the ‘<literal>:</literal>’ delimiter,
+ because of the <quote><literal>:</literal></quote> delimiter,
but if used in a date context is interpreted as the year
<literal>'2010-11-12'</literal>. The value
<literal>'10:45:15'</literal> is converted to
@@ -5212,7 +5212,7 @@
allowed values specified when the table is created.
<literal>SET</literal> column values that consist of multiple
set members are specified with members separated by commas
- (‘<literal>,</literal>’). A consequence of this is
+ (<quote><literal>,</literal></quote>). A consequence of this is
that <literal>SET</literal> member values should not themselves
contain commas.
</para>
Modified: trunk/refman-4.1/dba-core.xml
===================================================================
--- trunk/refman-4.1/dba-core.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/dba-core.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 19, Lines Added: 35, Lines Deleted: 35; 10620 bytes
@@ -3048,9 +3048,9 @@
that is too small to hold temporary tables. Starting from
MySQL 4.1.0, this option accepts several paths that are
used in round-robin fashion. Paths should be separated by
- colon characters (‘<literal>:</literal>’) on
+ colon characters (<quote><literal>:</literal></quote>) on
Unix and semicolon characters
- (‘<literal>;</literal>’) on Windows, NetWare,
+ (<quote><literal>;</literal></quote>) on Windows, NetWare,
and OS/2. If the MySQL server is acting as a replication
slave, you should not set <option>--tmpdir</option> to
point to a directory on a memory-based filesystem or to a
@@ -4020,9 +4020,9 @@
<listitem>
<para>
Positions 10, 13, and 14 (which by default are set to
- ‘<literal>:</literal>’,
- ‘<literal>&</literal>’, and
- ‘<literal>|</literal>’) are reserved for
+ <quote><literal>:</literal></quote>,
+ <quote><literal>&</literal></quote>, and
+ <quote><literal>|</literal></quote>) are reserved for
future extensions.
</para>
</listitem>
@@ -6621,8 +6621,8 @@
tables. Starting from MySQL 4.1, this variable can be set
to a list of several paths that are used in round-robin
fashion. Paths should be separated by colon characters
- (‘<literal>:</literal>’) on Unix and semicolon
- characters (‘<literal>;</literal>’) on
+ (<quote><literal>:</literal></quote>) on Unix and semicolon
+ characters (<quote><literal>;</literal></quote>) on
Windows, NetWare, and OS/2.
</para>
@@ -7187,7 +7187,7 @@
<para>
To get a list of variables whose name match a pattern, use the
- ‘<literal>%</literal>’ wildcard character in a
+ <quote><literal>%</literal></quote> wildcard character in a
<literal>LIKE</literal> clause:
</para>
@@ -7199,9 +7199,9 @@
<para>
Wildcard characters can be used in any position within the
pattern to be matched. Strictly speaking, because
- ‘<literal>_</literal>’ is a wildcard that matches
+ <quote><literal>_</literal></quote> is a wildcard that matches
any single character, you should escape it as
- ‘<literal>\_</literal>’ to match it literally. In
+ <quote><literal>\_</literal></quote> to match it literally. In
practice, this is rarely necessary.
</para>
@@ -8650,11 +8650,11 @@
</para>
<para>
- Treat ‘<literal>"</literal>’ as an identifier
+ Treat <quote><literal>"</literal></quote> as an identifier
quote character (like the
- ‘<literal>`</literal>’ quote character) and
+ <quote><literal>`</literal></quote> quote character) and
not as a string quote character. You can still use
- ‘<literal>`</literal>’ to quote identifiers
+ <quote><literal>`</literal></quote> to quote identifiers
with this mode enabled. With
<literal>ANSI_QUOTES</literal> enabled, you cannot use
double quotes to quote literal strings, because it is
@@ -8673,7 +8673,7 @@
<para>
Allow spaces between a function name and the
- ‘<literal>(</literal>’ character. This causes
+ <quote><literal>(</literal></quote> character. This causes
built-in function names to be treated as reserved words.
As a result, identifiers that are the same as function
names must be quoted as described in
@@ -12479,8 +12479,8 @@
<listitem>
<para>
Try to enter single and double quote marks
- (‘<literal>'</literal>’ and
- ‘<literal>"</literal>’) in all of your Web
+ (<quote><literal>'</literal></quote> and
+ <quote><literal>"</literal></quote>) in all of your Web
forms. If you get any kind of MySQL error, investigate
the problem right away.
</para>
@@ -12490,11 +12490,11 @@
<para>
Try to modify dynamic URLs by adding
<literal>%22</literal>
- (‘<literal>"</literal>’),
+ (<quote><literal>"</literal></quote>),
<literal>%23</literal>
- (‘<literal>#</literal>’), and
+ (<quote><literal>#</literal></quote>), and
<literal>%27</literal>
- (‘<literal>'</literal>’) to them.
+ (<quote><literal>'</literal></quote>) to them.
</para>
</listitem>
@@ -14955,8 +14955,8 @@
</indexterm>
You can use the wildcard characters
- ‘<literal>%</literal>’ and
- ‘<literal>_</literal>’ in
+ <quote><literal>%</literal></quote> and
+ <quote><literal>_</literal></quote> in
<literal>Host</literal> column values. These have the same
meaning as for pattern-matching operations performed with
the <literal>LIKE</literal> operator. For example, a
@@ -14972,7 +14972,7 @@
<para>
An overly broad host specifier such as
- ‘<literal>%</literal>’ constitutes a security
+ <quote><literal>%</literal></quote> constitutes a security
risk. The MySQL Enterprise Monitor provides safeguards
against this kind of vulnerability. For more information
see, <ulink url="&base-url-enterprise;advisors.html"/>.
@@ -15479,17 +15479,17 @@
<listitem>
<para>
- The wildcard characters ‘<literal>%</literal>’
- and ‘<literal>_</literal>’ can be used in the
+ The wildcard characters <quote><literal>%</literal></quote>
+ and <quote><literal>_</literal></quote> can be used in the
<literal>Host</literal> and <literal>Db</literal> columns of
either table. These have the same meaning as for
pattern-matching operations performed with the
<literal>LIKE</literal> operator. If you want to use either
character literally when granting privileges, you must
escape it with a backslash. For example, to include
- ‘<literal>_</literal>’ character as part of a
+ <quote><literal>_</literal></quote> character as part of a
database name, specify it as
- ‘<literal>\_</literal>’ in the
+ <quote><literal>\_</literal></quote> in the
<literal>GRANT</literal> statement.
</para>
</listitem>
@@ -15591,8 +15591,8 @@
<listitem>
<para>
- The wildcard characters ‘<literal>%</literal>’
- and ‘<literal>_</literal>’ can be used in the
+ The wildcard characters <quote><literal>%</literal></quote>
+ and <quote><literal>_</literal></quote> can be used in the
<literal>Host</literal> column. These have the same meaning
as for pattern-matching operations performed with the
<literal>LIKE</literal> operator.
@@ -16411,7 +16411,7 @@
could add an entry to the <literal>user</literal> table with
a <literal>Host</literal> value that contains a wildcard;
for example, <literal>'tcx.%'</literal>. However, use of
- hostnames ending with ‘<literal>%</literal>’ is
+ hostnames ending with <quote><literal>%</literal></quote> is
insecure and is <emphasis>not</emphasis> recommended.)
</para>
</listitem>
@@ -16446,8 +16446,8 @@
denied</literal>, remove from the <literal>user</literal>
table all entries that have <literal>Host</literal> values
containing wildcards (entries that contain
- ‘<literal>%</literal>’ or
- ‘<literal>_</literal>’). A very common error is
+ <quote><literal>%</literal></quote> or
+ <quote><literal>_</literal></quote>). A very common error is
to insert a new entry with
<literal>Host</literal>=<literal>'%'</literal> and
<literal>User</literal>=<literal>'<replaceable>some_user</replaceable>'</literal>,
@@ -16789,7 +16789,7 @@
<para>
A second difference is that password hashes in the new
format always begin with a
- ‘<literal>*</literal>’ character, whereas
+ <quote><literal>*</literal></quote> character, whereas
passwords in the old format never do.
</para>
</listitem>
@@ -17892,7 +17892,7 @@
If you want to give a specific user access from all machines in
a given domain (for example, <literal>mydomain.com</literal>),
you can issue a <literal>GRANT</literal> statement that uses the
- ‘<literal>%</literal>’ wildcard character in the
+ <quote><literal>%</literal></quote> wildcard character in the
host part of the account name:
</para>
@@ -18426,7 +18426,7 @@
</programlisting>
<para>
- The ‘<literal>*</literal>’ characters indicate
+ The <quote><literal>*</literal></quote> characters indicate
where you enter your password. The password is not displayed
as you enter it.
</para>
@@ -22286,7 +22286,7 @@
<listitem>
<para>
- Comments start with a ‘<literal>#</literal>’
+ Comments start with a <quote><literal>#</literal></quote>
character and continue to the end of the line.
</para>
</listitem>
Modified: trunk/refman-4.1/errors-problems.xml
===================================================================
--- trunk/refman-4.1/errors-problems.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/errors-problems.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 4, Lines Added: 8, Lines Deleted: 8; 2559 bytes
@@ -2307,7 +2307,7 @@
open files limit, you can edit the
<command>mysqld_safe</command> script. There is a
commented-out line <command>ulimit -n 256</command> in the
- script. You can remove the ‘<literal>#</literal>’
+ script. You can remove the <quote><literal>#</literal></quote>
character to uncomment this line, and change the number
<literal>256</literal> to set the number of file descriptors
to be made available to <command>mysqld</command>.
@@ -3391,8 +3391,8 @@
Starting from MySQL 4.1, the <option>--tmpdir</option> option
can be set to a list of several paths that are used in
round-robin fashion. Paths should be separated by colon
- characters (‘<literal>:</literal>’) on Unix and
- semicolon characters (‘<literal>;</literal>’) on
+ characters (<quote><literal>:</literal></quote>) on Unix and
+ semicolon characters (<quote><literal>;</literal></quote>) on
Windows, NetWare, and OS/2.
<emphasis role="bold">Note</emphasis>: To spread the load
effectively, these paths should be located on different
@@ -3706,9 +3706,9 @@
Simple comparison operations (<literal>>=, >, =, <,
<=</literal>, sorting, and grouping) are based on each
character's <quote>sort value.</quote> Characters with the
- same sort value (such as ‘<literal>E</literal>’,
- ‘<literal>e</literal>’, and
- ‘<literal>é</literal>’) are treated as the
+ same sort value (such as <quote><literal>E</literal></quote>,
+ <quote><literal>e</literal></quote>, and
+ <quote><literal>é</literal></quote>) are treated as the
same character.
</para>
@@ -5486,8 +5486,8 @@
<listitem>
<para>
- You can't use ‘<literal>_</literal>’ or
- ‘<literal>%</literal>’ with
+ You can't use <quote><literal>_</literal></quote> or
+ <quote><literal>%</literal></quote> with
<literal>ESCAPE</literal> in <literal>LIKE ...
ESCAPE</literal>.
</para>
Modified: trunk/refman-4.1/functions-core.xml
===================================================================
--- trunk/refman-4.1/functions-core.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/functions-core.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 19, Lines Added: 34, Lines Deleted: 34; 11969 bytes
@@ -2444,7 +2444,7 @@
Strings are added to the result from left to right, separated
by the <replaceable>separator</replaceable> string (the
default being the comma character
- ‘<literal>,</literal>’). The number of bits
+ <quote><literal>,</literal></quote>). The number of bits
examined is given by <replaceable>number_of_bits</replaceable>
(defaults to 64).
</para>
@@ -2538,7 +2538,7 @@
<replaceable>strlist</replaceable> consisting of
<replaceable>N</replaceable> substrings. A string list is a
string composed of substrings separated by
- ‘<literal>,</literal>’ characters. If the first
+ <quote><literal>,</literal></quote> characters. If the first
argument is a constant string and the second is a column of
type <literal>SET</literal>, the
<literal>FIND_IN_SET()</literal> function is optimized to use
@@ -2549,7 +2549,7 @@
Returns <literal>NULL</literal> if either argument is
<literal>NULL</literal>. This function does not work properly
if the first argument contains a comma
- (‘<literal>,</literal>’) character.
+ (<quote><literal>,</literal></quote>) character.
</para>
<remark role="help-description-end"/>
@@ -3076,7 +3076,7 @@
<para>
Returns a set value (a string containing substrings separated
- by ‘<literal>,</literal>’ characters) consisting
+ by <quote><literal>,</literal></quote> characters) consisting
of the strings that have the corresponding bit in
<replaceable>bits</replaceable> set.
<replaceable>str1</replaceable> corresponds to bit 0,
@@ -3285,8 +3285,8 @@
Quotes a string to produce a result that can be used as a
properly escaped data value in an SQL statement. The string is
returned enclosed by single quotes and with each instance of
- single quote (‘<literal>'</literal>’), backslash
- (‘<literal>\</literal>’), ASCII
+ single quote (<quote><literal>'</literal></quote>), backslash
+ (<quote><literal>\</literal></quote>), ASCII
<literal>NUL</literal>, and Control-Z preceded by a backslash.
If the argument is <literal>NULL</literal>, the return value
is the word <quote>NULL</quote> without enclosing single
@@ -4161,7 +4161,7 @@
To test for literal instances of a wildcard character,
precede it by the escape character. If you do not specify
the <literal>ESCAPE</literal> character,
- ‘<literal>\</literal>’ is assumed.
+ <quote><literal>\</literal></quote> is assumed.
</para>
<informaltable>
@@ -4175,11 +4175,11 @@
</row>
<row>
<entry><literal>\%</literal></entry>
- <entry>Matches one ‘<literal>%</literal>’ character</entry>
+ <entry>Matches one <quote><literal>%</literal></quote> character</entry>
</row>
<row>
<entry><literal>\_</literal></entry>
- <entry>Matches one ‘<literal>_</literal>’ character</entry>
+ <entry>Matches one <quote><literal>_</literal></quote> character</entry>
</row>
</tbody>
</tgroup>
@@ -4229,19 +4229,19 @@
<note>
<para>
Because MySQL uses C escape syntax in strings (for
- example, ‘<literal>\n</literal>’ to represent
+ example, <quote><literal>\n</literal></quote> to represent
a newline character), you must double any
- ‘<literal>\</literal>’ that you use in
+ <quote><literal>\</literal></quote> that you use in
<literal>LIKE</literal> strings. For example, to search
- for ‘<literal>\n</literal>’, specify it as
- ‘<literal>\\n</literal>’. To search for
- ‘<literal>\</literal>’, specify it as
- ‘<literal>\\\\</literal>’; this is because the
+ for <quote><literal>\n</literal></quote>, specify it as
+ <quote><literal>\\n</literal></quote>. To search for
+ <quote><literal>\</literal></quote>, specify it as
+ <quote><literal>\\\\</literal></quote>; this is because the
backslashes are stripped once by the parser and again when
the pattern match is made, leaving a single backslash to
be matched against. (Exception: At the end of the pattern
string, backslash can be specified as
- ‘<literal>\\</literal>’. At the end of the
+ <quote><literal>\\</literal></quote>. At the end of the
string, backslash stands for itself because there is
nothing following to escape.)
</para>
@@ -4405,9 +4405,9 @@
<note>
<para>
Because MySQL uses the C escape syntax in strings (for
- example, ‘<literal>\n</literal>’ to represent
+ example, <quote><literal>\n</literal></quote> to represent
the newline character), you must double any
- ‘<literal>\</literal>’ that you use in your
+ <quote><literal>\</literal></quote> that you use in your
<literal>REGEXP</literal> strings.
</para>
</note>
@@ -7460,7 +7460,7 @@
is an expression specifying the interval value to be added or
subtracted from the starting date.
<replaceable>expr</replaceable> is a string; it may start with
- a ‘<literal>-</literal>’ for negative intervals.
+ a <quote><literal>-</literal></quote> for negative intervals.
<replaceable>unit</replaceable> is a keyword indicating the
units in which the expression should be interpreted.
</para>
@@ -7756,9 +7756,9 @@
<para>
The following specifiers may be used in the
<replaceable>format</replaceable> string. As of MySQL 3.23,
- the ‘<literal>%</literal>’ character is required
+ the <quote><literal>%</literal></quote> character is required
before format specifier characters. In earlier versions of
- MySQL, ‘<literal>%</literal>’ was optional.
+ MySQL, <quote><literal>%</literal></quote> was optional.
</para>
<informaltable>
@@ -7907,12 +7907,12 @@
</row>
<row>
<entry><literal>%%</literal></entry>
- <entry>A literal ‘<literal>%</literal>’ character</entry>
+ <entry>A literal <quote><literal>%</literal></quote> character</entry>
</row>
<row>
<entry><literal>%<replaceable>x</replaceable></literal></entry>
<entry><replaceable>x</replaceable>, for any
- ‘<replaceable>x</replaceable>’ not listed
+ <quote><replaceable>x</replaceable></quote> not listed
above</entry>
</row>
</tbody>
@@ -10550,7 +10550,7 @@
The MySQL <literal>FULLTEXT</literal> implementation regards any
sequence of true word characters (letters, digits, and
underscores) as a word. That sequence may also contain apostrophes
- (‘<literal>'</literal>’), but not more than one in a
+ (<quote><literal>'</literal></quote>), but not more than one in a
row. This means that <literal>aaa'bbb</literal> is regarded as one
word, but <literal>aaa''bbb</literal> is regarded as two words.
Apostrophes at the beginning or the end of a word are stripped by
@@ -10562,15 +10562,15 @@
<para>
The <literal>FULLTEXT</literal> parser determines where words
start and end by looking for certain delimiter characters; for
- example, ‘<literal> </literal>’ (space),
- ‘<literal>,</literal>’ (comma), and
- ‘<literal>.</literal>’ (period). If words are not
+ example, <quote><literal> </literal></quote> (space),
+ <quote><literal>,</literal></quote> (comma), and
+ <quote><literal>.</literal></quote> (period). If words are not
separated by delimiters (as in, for example, Chinese), the
<literal>FULLTEXT</literal> parser cannot determine where a word
begins or ends. To be able to add words or other indexed terms in
such languages to a <literal>FULLTEXT</literal> index, you must
preprocess them so that they are separated by some arbitrary
- delimiter such as ‘<literal>"</literal>’.
+ delimiter such as <quote><literal>"</literal></quote>.
</para>
<para>
@@ -10879,7 +10879,7 @@
<para>
A phrase that is enclosed within double quote
- (‘<literal>"</literal>’) characters matches only
+ (<quote><literal>"</literal></quote>) characters matches only
rows that contain the phrase <emphasis>literally, as it was
typed</emphasis>. The full-text engine splits the phrase
into words, performs a search in the
@@ -11002,7 +11002,7 @@
words</quote> (for example, rows that contain <quote>some
words of wisdom</quote> but not <quote>some noise
words</quote>). Note that the
- ‘<literal>"</literal>’ characters that enclose
+ <quote><literal>"</literal></quote> characters that enclose
the phrase are operator characters that delimit the phrase.
They are not the quotes that enclose the search string
itself.
@@ -12028,8 +12028,8 @@
The stopword list is free-form. That is, you may use any
non-alphanumeric character such as newline, space, or comma
to separate stopwords. Exceptions are the underscore
- character (‘<literal>_</literal>’) and a single
- apostrophe (‘<literal>'</literal>’) which are
+ character (<quote><literal>_</literal></quote>) and a single
+ apostrophe (<quote><literal>'</literal></quote>) which are
treated as part of a word. The character set of the stopword
list is the server's default character set; see
<xref linkend="charset-server"/>.
@@ -13212,7 +13212,7 @@
Non-empty strings are stored as a four-byte length of
the uncompressed string (low byte first), followed by
the compressed string. If the string ends with space, an
- extra ‘<literal>.</literal>’ character is
+ extra <quote><literal>.</literal></quote> character is
added to avoid problems with endspace trimming should
the result be stored in a <literal>CHAR</literal> or
<literal>VARCHAR</literal> column. (Use of
@@ -15846,7 +15846,7 @@
keyword. <literal>SEPARATOR</literal> is followed by the
string value that should be inserted between values of
result. The default is a comma
- (‘<literal>,</literal>’). You can eliminate the
+ (<quote><literal>,</literal></quote>). You can eliminate the
separator altogether by specifying <literal>SEPARATOR
''</literal>.
</para>
Modified: trunk/refman-4.1/installing.xml
===================================================================
--- trunk/refman-4.1/installing.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/installing.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1640 bytes
@@ -5611,17 +5611,17 @@
<listitem>
<para>
- <emphasis role="bold">The ‘<literal>\</literal>’
+ <emphasis role="bold">The <quote><literal>\</literal></quote>
pathname separator character</emphasis>
</para>
<para>
Pathname components in Windows are separated by the
- ‘<literal>\</literal>’ character, which is also
+ <quote><literal>\</literal></quote> character, which is also
the escape character in MySQL. If you are using
<literal>LOAD DATA INFILE</literal> or <literal>SELECT ...
INTO OUTFILE</literal>, use Unix-style filenames with
- ‘<literal>/</literal>’ characters:
+ <quote><literal>/</literal></quote> characters:
</para>
<programlisting>
@@ -5631,7 +5631,7 @@
<para>
Alternatively, you must double the
- ‘<literal>\</literal>’ character:
+ <quote><literal>\</literal></quote> character:
</para>
<programlisting>
@@ -20327,7 +20327,7 @@
<para>
Each field consists of a mandatory flag character followed by an
- optional ‘<literal>,</literal>’ and comma-separated
+ optional <quote><literal>,</literal></quote> and comma-separated
list of modifiers:
</para>
Modified: trunk/refman-4.1/introduction.xml
===================================================================
--- trunk/refman-4.1/introduction.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/introduction.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 9, Lines Added: 21, Lines Deleted: 21; 5533 bytes
@@ -1316,7 +1316,7 @@
<para>
If you add a version number after the
- ‘<literal>!</literal>’ character, the syntax within
+ <quote><literal>!</literal></quote> character, the syntax within
the comment is executed only if the MySQL version is greater
than or equal to the specified version number. The
<literal>TEMPORARY</literal> keyword in the following comment is
@@ -1397,8 +1397,8 @@
<para>
Database and table names cannot contain pathname separator
- characters (‘<literal>/</literal>’,
- ‘<literal>\</literal>’).
+ characters (<quote><literal>/</literal></quote>,
+ <quote><literal>\</literal></quote>).
</para>
</listitem>
@@ -1412,20 +1412,20 @@
<listitem>
<para>
By default, strings can be enclosed by either
- ‘<literal>"</literal>’ or
- ‘<literal>'</literal>’, not just by
- ‘<literal>'</literal>’. (If the
+ <quote><literal>"</literal></quote> or
+ <quote><literal>'</literal></quote>, not just by
+ <quote><literal>'</literal></quote>. (If the
<literal>ANSI_QUOTES</literal> SQL mode is enabled,
strings can be enclosed only by
- ‘<literal>'</literal>’ and the server
+ <quote><literal>'</literal></quote> and the server
interprets strings enclosed by
- ‘<literal>"</literal>’ as identifiers.)
+ <quote><literal>"</literal></quote> as identifiers.)
</para>
</listitem>
<listitem>
<para>
- ‘<literal>\</literal>’ is the escape
+ <quote><literal>\</literal></quote> is the escape
character in strings.
</para>
</listitem>
@@ -2648,12 +2648,12 @@
</para>
<para>
- Standard SQL uses ‘<option>--</option>’ as a
+ Standard SQL uses <quote><option>--</option></quote> as a
start-comment sequence. MySQL Server uses
- ‘<literal>#</literal>’ as the start comment
+ <quote><literal>#</literal></quote> as the start comment
character. MySQL Server 3.23.3 and up also supports a variant
- of the ‘<literal>--</literal>’ comment style. That
- is, the ‘<literal>--</literal>’ start-comment
+ of the <quote><literal>--</literal></quote> comment style. That
+ is, the <quote><literal>--</literal></quote> start-comment
sequence must be followed by a space (or by a control
character such as a newline). The space is required to prevent
problems with automatically generated SQL queries that use
@@ -2677,7 +2677,7 @@
<para>
<literal>credit--1</literal> is a legal expression in SQL, but
- ‘<literal>--</literal>’ is interpreted as the
+ <quote><literal>--</literal></quote> is interpreted as the
start of a comment, part of the expression is discarded. The
result is a statement that has a completely different meaning
than intended:
@@ -2690,13 +2690,13 @@
<para>
The statement produces no change in value at all. This
illustrates that allowing comments to start with
- ‘<literal>--</literal>’ can have serious
+ <quote><literal>--</literal></quote> can have serious
consequences.
</para>
<para>
Using our implementation requires a space following the
- ‘<literal>--</literal>’ in order for it to be
+ <quote><literal>--</literal></quote> 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.
@@ -2705,7 +2705,7 @@
<para>
Another safe feature is that the <command>mysql</command>
command-line client ignores lines that start with
- ‘<literal>--</literal>’.
+ <quote><literal>--</literal></quote>.
</para>
<para>
@@ -2715,9 +2715,9 @@
<para>
If you have an SQL script in a text file that contains
- ‘<literal>--</literal>’ comments, you should use
+ <quote><literal>--</literal></quote> comments, you should use
the <command>replace</command> utility as follows to convert
- the comments to use ‘<literal>#</literal>’
+ the comments to use <quote><literal>#</literal></quote>
characters before executing the script:
</para>
@@ -2736,8 +2736,8 @@
<para>
You can also edit the script file <quote>in place</quote> to
- change the ‘<literal>--</literal>’ comments to
- ‘<literal>#</literal>’ comments:
+ change the <quote><literal>--</literal></quote> comments to
+ <quote><literal>#</literal></quote> comments:
</para>
<programlisting>
Modified: trunk/refman-4.1/language-structure.xml
===================================================================
--- trunk/refman-4.1/language-structure.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/language-structure.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 23, Lines Added: 66, Lines Deleted: 66; 15984 bytes
@@ -91,8 +91,8 @@
<para>
A string is a sequence of bytes or characters, enclosed within
- either single quote (‘<literal>'</literal>’) or
- double quote (‘<literal>"</literal>’) characters.
+ either single quote (<quote><literal>'</literal></quote>) or
+ double quote (<quote><literal>"</literal></quote>) characters.
Examples:
</para>
@@ -170,7 +170,7 @@
<para>
Within a string, certain sequences have special meaning. Each of
these sequences begins with a backslash
- (‘<literal>\</literal>’), known as the
+ (<quote><literal>\</literal></quote>), known as the
<emphasis>escape character</emphasis>. MySQL recognizes the
following escape sequences:
</para>
@@ -202,7 +202,7 @@
<indexterm>
<primary>single quote (\')</primary>
</indexterm></entry>
- <entry>A single quote (‘<literal>'</literal>’) character.</entry>
+ <entry>A single quote (<quote><literal>'</literal></quote>) character.</entry>
</row>
<row>
<entry><literal>\"</literal>
@@ -214,7 +214,7 @@
<indexterm>
<primary>double quote (\")</primary>
</indexterm></entry>
- <entry>A double quote (‘<literal>"</literal>’) character.</entry>
+ <entry>A double quote (<quote><literal>"</literal></quote>) character.</entry>
</row>
<row>
<entry><literal>\b</literal>
@@ -298,7 +298,7 @@
<indexterm>
<primary>escape (\\)</primary>
</indexterm></entry>
- <entry>A backslash (‘<literal>\</literal>’) character.</entry>
+ <entry>A backslash (<quote><literal>\</literal></quote>) character.</entry>
</row>
<row>
<entry><literal>\%</literal>
@@ -310,7 +310,7 @@
<indexterm>
<primary>Wildcard character (%)</primary>
</indexterm></entry>
- <entry>A ‘<literal>%</literal>’ character. See note following the
+ <entry>A <quote><literal>%</literal></quote> character. See note following the
table.</entry>
</row>
<row>
@@ -323,7 +323,7 @@
<indexterm>
<primary>Wildcard character (_)</primary>
</indexterm></entry>
- <entry>A ‘<literal>_</literal>’ character. See note following the
+ <entry>A <quote><literal>_</literal></quote> character. See note following the
table.</entry>
</row>
</tbody>
@@ -333,20 +333,20 @@
<para>
For all other escape sequences, backslash is ignored. That is,
the escaped character is interpreted as if it was not escaped.
- For example, ‘<literal>\x</literal>’ is just
- ‘<literal>x</literal>’.
+ For example, <quote><literal>\x</literal></quote> is just
+ <quote><literal>x</literal></quote>.
</para>
<para>
These sequences are case sensitive. For example,
- ‘<literal>\b</literal>’ is interpreted as a
- backspace, but ‘<literal>\B</literal>’ is
- interpreted as ‘<literal>B</literal>’.
+ <quote><literal>\b</literal></quote> is interpreted as a
+ backspace, but <quote><literal>\B</literal></quote> is
+ interpreted as <quote><literal>B</literal></quote>.
</para>
<para>
The ASCII 26 character can be encoded as
- ‘<literal>\Z</literal>’ to enable you to work around
+ <quote><literal>\Z</literal></quote> to enable you to work around
the problem that ASCII 26 stands for END-OF-FILE on Windows.
ASCII 26 within a file causes problems if you try to use
<literal>mysql <replaceable>db_name</replaceable> <
@@ -362,20 +362,20 @@
</para>
<para>
- The ‘<literal>\%</literal>’ and
- ‘<literal>\_</literal>’ sequences are used to search
- for literal instances of ‘<literal>%</literal>’ and
- ‘<literal>_</literal>’ in pattern-matching contexts
+ The <quote><literal>\%</literal></quote> and
+ <quote><literal>\_</literal></quote> sequences are used to search
+ for literal instances of <quote><literal>%</literal></quote> and
+ <quote><literal>_</literal></quote> in pattern-matching contexts
where they would otherwise be interpreted as wildcard
characters. See the description of the <literal>LIKE</literal>
operator in <xref linkend="string-comparison-functions"/>. If
- you use ‘<literal>\%</literal>’ or
- ‘<literal>\_</literal>’ in non-pattern-matching
+ you use <quote><literal>\%</literal></quote> or
+ <quote><literal>\_</literal></quote> in non-pattern-matching
contexts, they evaluate to the strings
- ‘<literal>\%</literal>’ and
- ‘<literal>\_</literal>’, not to
- ‘<literal>%</literal>’ and
- ‘<literal>_</literal>’.
+ <quote><literal>\%</literal></quote> and
+ <quote><literal>\_</literal></quote>, not to
+ <quote><literal>%</literal></quote> and
+ <quote><literal>_</literal></quote>.
</para>
<indexterm>
@@ -392,34 +392,34 @@
<listitem>
<para>
- A ‘<literal>'</literal>’ inside a string quoted
- with ‘<literal>'</literal>’ may be written as
- ‘<literal>''</literal>’.
+ A <quote><literal>'</literal></quote> inside a string quoted
+ with <quote><literal>'</literal></quote> may be written as
+ <quote><literal>''</literal></quote>.
</para>
</listitem>
<listitem>
<para>
- A ‘<literal>"</literal>’ inside a string quoted
- with ‘<literal>"</literal>’ may be written as
- ‘<literal>""</literal>’.
+ A <quote><literal>"</literal></quote> inside a string quoted
+ with <quote><literal>"</literal></quote> may be written as
+ <quote><literal>""</literal></quote>.
</para>
</listitem>
<listitem>
<para>
Precede the quote character by an escape character
- (‘<literal>\</literal>’).
+ (<quote><literal>\</literal></quote>).
</para>
</listitem>
<listitem>
<para>
- A ‘<literal>'</literal>’ inside a string quoted
- with ‘<literal>"</literal>’ needs no special
+ A <quote><literal>'</literal></quote> inside a string quoted
+ with <quote><literal>"</literal></quote> needs no special
treatment and need not be doubled or escaped. In the same
- way, ‘<literal>"</literal>’ inside a string
- quoted with ‘<literal>'</literal>’ needs no
+ way, <quote><literal>"</literal></quote> inside a string
+ quoted with <quote><literal>'</literal></quote> needs no
special treatment.
</para>
</listitem>
@@ -474,24 +474,24 @@
<row>
<entry><literal>NUL</literal></entry>
<entry><literal>NUL</literal> byte (ASCII 0). Represent this character by
- ‘<literal>\0</literal>’ (a backslash
- followed by an ASCII ‘<literal>0</literal>’
+ <quote><literal>\0</literal></quote> (a backslash
+ followed by an ASCII <quote><literal>0</literal></quote>
character).</entry>
</row>
<row>
<entry><literal>\</literal></entry>
<entry>Backslash (ASCII 92). Represent this character by
- ‘<literal>\\</literal>’.</entry>
+ <quote><literal>\\</literal></quote>.</entry>
</row>
<row>
<entry><literal>'</literal></entry>
<entry>Single quote (ASCII 39). Represent this character by
- ‘<literal>\'</literal>’.</entry>
+ <quote><literal>\'</literal></quote>.</entry>
</row>
<row>
<entry><literal>"</literal></entry>
<entry>Double quote (ASCII 34). Represent this character by
- ‘<literal>\"</literal>’.</entry>
+ <quote><literal>\"</literal></quote>.</entry>
</row>
</tbody>
</tgroup>
@@ -587,10 +587,10 @@
<para>
Integers are represented as a sequence of digits. Floats use
- ‘<literal>.</literal>’ as a decimal separator.
+ <quote><literal>.</literal></quote> as a decimal separator.
Either type of number may be preceded by
- ‘<literal>-</literal>’ or
- ‘<literal>+</literal>’ to indicate a negative or
+ <quote><literal>-</literal></quote> or
+ <quote><literal>+</literal></quote> to indicate a negative or
positive value, respectively
</para>
@@ -867,18 +867,18 @@
<listitem>
<para>
Database names cannot contain
- ‘<literal>/</literal>’,
- ‘<literal>\</literal>’,
- ‘<literal>.</literal>’, or characters that are not
+ <quote><literal>/</literal></quote>,
+ <quote><literal>\</literal></quote>,
+ <quote><literal>.</literal></quote>, or characters that are not
allowed in a directory name.
</para>
</listitem>
<listitem>
<para>
- Table names cannot contain ‘<literal>/</literal>’,
- ‘<literal>\</literal>’,
- ‘<literal>.</literal>’, or characters that are not
+ Table names cannot contain <quote><literal>/</literal></quote>,
+ <quote><literal>\</literal></quote>,
+ <quote><literal>.</literal></quote>, or characters that are not
allowed in a filename.
</para>
</listitem>
@@ -933,13 +933,13 @@
reserved.) For a list of reserved words, see
<xref linkend="reserved-words"/>. Special characters are those
outside the set of alphanumeric characters from the current
- character set, ‘<literal>_</literal>’, and
- ‘<literal>$</literal>’.
+ character set, <quote><literal>_</literal></quote>, and
+ <quote><literal>$</literal></quote>.
</para>
<para>
The identifier quote character is the backtick
- (‘<literal>`</literal>’):
+ (<quote><literal>`</literal></quote>):
</para>
<programlisting>
@@ -996,8 +996,8 @@
<listitem>
<para>
A name may consist of alphanumeric characters from the current
- character set, ‘<literal>_</literal>’, and
- ‘<literal>$</literal>’. The default character set
+ character set, <quote><literal>_</literal></quote>, and
+ <quote><literal>$</literal></quote>. The default character set
is cp1252 (Latin1). This may be changed with the
<option>--default-character-set</option> option to
<command>mysqld</command>. See
@@ -1016,7 +1016,7 @@
<listitem>
<para>
- You cannot use the ‘<literal>.</literal>’
+ You cannot use the <quote><literal>.</literal></quote>
character in names because it is used to extend the format by
which you can refer to columns (see
<xref linkend="identifier-qualifiers"/>).
@@ -1064,7 +1064,7 @@
MySQL allows names that consist of a single identifier or
multiple identifiers. The components of a multiple-part name
should be separated by period
- (‘<literal>.</literal>’) characters. The initial
+ (<quote><literal>.</literal></quote>) characters. The initial
parts of a multiple-part name act as qualifiers that affect the
context within which the final identifier is interpreted.
</para>
@@ -1153,7 +1153,7 @@
<replaceable>tbl_name</replaceable> in the default database.
This syntax is accepted for ODBC compatibility because some ODBC
programs prefix table names with a
- ‘<literal>.</literal>’ character.
+ <quote><literal>.</literal></quote> character.
</para>
</section>
@@ -1458,7 +1458,7 @@
<para>
To use the name as a function call in an expression, there
must be no whitespace between the name and the following
- ‘<literal>(</literal>’ parenthesis character.
+ <quote><literal>(</literal></quote> parenthesis character.
</para>
</listitem>
@@ -1730,7 +1730,7 @@
<literal>COUNT</literal> is acceptable as a column name. However,
by default, no whitespace is allowed in function invocations
between the function name and the following
- ‘<literal>(</literal>’ character. This requirement
+ <quote><literal>(</literal></quote> character. This requirement
enables the parser to distinguish whether the name is used in a
function call or in non-function context. For further detail on
recognition of function names, see
@@ -1849,9 +1849,9 @@
<literal>@<replaceable>var_name</replaceable></literal>, where the
variable name <replaceable>var_name</replaceable> may consist of
alphanumeric characters from the current character set,
- ‘<literal>.</literal>’,
- ‘<literal>_</literal>’, and
- ‘<literal>$</literal>’. The default character set is
+ <quote><literal>.</literal></quote>,
+ <quote><literal>_</literal></quote>, and
+ <quote><literal>$</literal></quote>. The default character set is
<literal>latin1</literal> (cp1252 West European). This may be
changed with the <option>--default-character-set</option> option
to <command>mysqld</command>. See
@@ -2091,17 +2091,17 @@
<listitem>
<para>
- From a ‘<literal>#</literal>’ character to the end
+ From a <quote><literal>#</literal></quote> character to the end
of the line.
</para>
</listitem>
<listitem>
<para>
- From a ‘<literal>-- </literal>’ sequence to
+ From a <quote><literal>-- </literal></quote> sequence to
the end of the line. This style is supported as of MySQL
3.23.3. In MySQL, the
- <squo;<literal>-- </literal>’ (double-dash)
+ <quote><literal>-- </literal></quote> (double-dash)
comment style requires the second dash to be followed by at
least one whitespace or control character (such as a space,
tab, newline, and so on). This syntax differs slightly from
@@ -2162,7 +2162,7 @@
<para>
If you add a version number after the
- ‘<literal>!</literal>’ character, the syntax within
+ <quote><literal>!</literal></quote> character, the syntax within
the comment is executed only if the MySQL version is greater than
or equal to the specified version number. The
<literal>TEMPORARY</literal> keyword in the following comment is
Modified: trunk/refman-4.1/mysql-cluster-configuration.xml
===================================================================
--- trunk/refman-4.1/mysql-cluster-configuration.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/mysql-cluster-configuration.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 1026 bytes
@@ -556,8 +556,8 @@
square brackets), followed by the appropriate parameter names
and values. One deviation from the standard INI format is that
the parameter name and value can be separated by a colon
- (‘<literal>:</literal>’) as well as the equals sign
- (‘<literal>=</literal>’). Another deviation is that
+ (<quote><literal>:</literal></quote>) as well as the equals sign
+ (<quote><literal>=</literal></quote>). Another deviation is that
sections are not uniquely identified by section name. Instead,
unique sections (such as two different nodes of the same type)
are identified by a unique ID specified as a parameter within
Modified: trunk/refman-4.1/news-3.22.xml
===================================================================
--- trunk/refman-4.1/news-3.22.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/news-3.22.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 4, Lines Added: 6, Lines Deleted: 6; 1904 bytes
@@ -1173,8 +1173,8 @@
<listitem>
<para>
The hostname in <literal>user@hostname</literal> can now
- include ‘<literal>.</literal>’ and
- ‘<literal>-</literal>’ without quotes in the
+ include <quote><literal>.</literal></quote> and
+ <quote><literal>-</literal></quote> without quotes in the
context of the <literal>GRANT</literal>,
<literal>REVOKE</literal> and <literal>SET PASSWORD FOR
...</literal> statements.
@@ -1748,7 +1748,7 @@
<para>
Added connect option <literal>CLIENT_IGNORE_SPACE</literal> to
allow use of spaces after function names and before
- ‘<literal>(</literal>’ (Powerbuilder requires
+ <quote><literal>(</literal></quote> (Powerbuilder requires
this). This makes all function names reserved words.
</para>
</listitem>
@@ -2021,9 +2021,9 @@
<listitem>
<para>
<command>mysqld</command> now ignores trailing
- ‘<literal>;</literal>’ characters in queries. This
+ <quote><literal>;</literal></quote> characters in queries. This
is to make it easier to migrate from some other SQL servers
- that require the trailing ‘<literal>;</literal>’.
+ that require the trailing <quote><literal>;</literal></quote>.
</para>
</listitem>
@@ -2204,7 +2204,7 @@
<listitem>
<para>
- Allow ‘<literal>$</literal>’ in identifiers.
+ Allow <quote><literal>$</literal></quote> in identifiers.
</para>
</listitem>
Modified: trunk/refman-4.1/news-3.23.xml
===================================================================
--- trunk/refman-4.1/news-3.23.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/news-3.23.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 3, Lines Added: 3, Lines Deleted: 3; 1272 bytes
@@ -3248,7 +3248,7 @@
<listitem>
<para>
Fixed a bug that allowed use of database names containing a
- ‘<literal>.</literal>’ character. This fixes a
+ <quote><literal>.</literal></quote> character. This fixes a
serious security issue when <command>mysqld</command> is run
as root.
(<ulink url="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2001-0407">CVE-2001-0407</ulink>)
@@ -7033,7 +7033,7 @@
<listitem>
<para>
- Removed extra ‘<literal>)</literal>’ from the
+ Removed extra <quote><literal>)</literal></quote> from the
output of <literal>SHOW GRANTS</literal>.
</para>
</listitem>
@@ -8502,7 +8502,7 @@
<listitem>
<para>
<literal>DATE_FORMAT()</literal> now requires
- ‘<literal>%</literal>’ before any format
+ <quote><literal>%</literal></quote> before any format
character.
</para>
</listitem>
Modified: trunk/refman-4.1/news-4.0.xml
===================================================================
--- trunk/refman-4.1/news-4.0.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/news-4.0.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 5, Lines Added: 6, Lines Deleted: 6; 1964 bytes
@@ -1714,7 +1714,7 @@
InnoDB: Fixed a bug in the InnoDB <literal>FOREIGN
KEY</literal> parser that prevented <literal>ALTER
TABLE</literal> of tables containing
- ‘<literal>#</literal>’ in their names. (Bug #5856)
+ <quote><literal>#</literal></quote> in their names. (Bug #5856)
</para>
</listitem>
@@ -3536,7 +3536,7 @@
<listitem>
<para>
Fixed a buffer overflow error that occurred with prepended
- ‘<literal>0</literal>’ characters in some columns
+ <quote><literal>0</literal></quote> characters in some columns
of type <literal>DECIMAL</literal>. (Bug #2128)
</para>
</listitem>
@@ -3589,7 +3589,7 @@
<listitem>
<para>
- Fixed bug in prepending ‘<literal>0</literal>’
+ Fixed bug in prepending <quote><literal>0</literal></quote>
characters to <literal>DECIMAL</literal> column values.
</para>
</listitem>
@@ -5610,8 +5610,8 @@
<listitem>
<para>
Fixed <command>mysql</command> parser not to erroneously
- interpret ‘<literal>'</literal>’ or
- ‘<literal>"</literal>’ characters within
+ interpret <quote><literal>'</literal></quote> or
+ <quote><literal>"</literal></quote> characters within
<literal>/* ... */</literal> comment as beginning a quoted
string.
</para>
@@ -8361,7 +8361,7 @@
<listitem>
<para>
Don't allow database names that contain
- ‘<literal>\</literal>’.
+ <quote><literal>\</literal></quote>.
</para>
</listitem>
Modified: trunk/refman-4.1/news-4.1.xml
===================================================================
--- trunk/refman-4.1/news-4.1.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/news-4.1.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 8, Lines Added: 12, Lines Deleted: 12; 3866 bytes
@@ -6200,7 +6200,7 @@
or <option>--datadir</option> didn't work on Japanese Windows
machines for directory names containing multi-byte characters
having a second byte of <literal>0x5C</literal>
- (‘<literal>\</literal>’). (Bug #5439)
+ (<quote><literal>\</literal></quote>). (Bug #5439)
</para>
</listitem>
@@ -6374,7 +6374,7 @@
<listitem>
<para>
For prepared statements, the SQL parser did not disallow
- ‘<literal>?</literal>’ parameter markers
+ <quote><literal>?</literal></quote> parameter markers
immediately adjacent to other tokens, which could result in
malformed statements in the binary log. (For example,
<literal>SELECT * FROM t WHERE? = 1</literal> could become
@@ -8413,8 +8413,8 @@
<para>
Fixed <literal>utf8_spanish2_ci</literal> and
<literal>ucs2_spanish2_ci</literal> collations to not consider
- ‘<literal>r</literal>’ equal to
- ‘<literal>rr</literal>’. If you upgrade to this
+ <quote><literal>r</literal></quote> equal to
+ <quote><literal>rr</literal></quote>. If you upgrade to this
version from an earlier version, you should rebuild the
indexes of affected tables. (Bug #9269)
</para>
@@ -8535,8 +8535,8 @@
with single-backslash pathname separators. This would cause
syntax errors when importing the dump file.
<command>mysqldump</command> now changes
- ‘<literal>\</literal>’ to
- ‘<literal>/</literal>’ in the pathnames on
+ <quote><literal>\</literal></quote> to
+ <quote><literal>/</literal></quote> in the pathnames on
Windows. (Bug #6660)
</para>
</listitem>
@@ -8635,8 +8635,8 @@
<listitem>
<para>
<command>mysqldump</command> misinterpreted
- ‘<literal>_</literal>’ and
- ‘<literal>%</literal>’ characters in the names of
+ <quote><literal>_</literal></quote> and
+ <quote><literal>%</literal></quote> characters in the names of
tables to be dumped as wildcard characters. (Bug #9123)
</para>
</listitem>
@@ -8945,9 +8945,9 @@
<listitem>
<para>
In string literals with an escape character
- (‘<literal>\</literal>’) followed by a multi-byte
+ (<quote><literal>\</literal></quote>) followed by a multi-byte
character that has a second byte of
- ‘<literal>\</literal>’, the literal was not
+ <quote><literal>\</literal></quote>, the literal was not
interpreted correctly. The next character now is escaped, not
just the next byte. (Bug #8303)
</para>
@@ -11347,7 +11347,7 @@
InnoDB: Fixed a bug in the InnoDB <literal>FOREIGN
KEY</literal> parser that prevented <literal>ALTER
TABLE</literal> of tables containing
- ‘<literal>#</literal>’ in their names. (Bug #5856)
+ <quote><literal>#</literal></quote> in their names. (Bug #5856)
</para>
</listitem>
@@ -14616,7 +14616,7 @@
<listitem>
<para>
Fixed <command>mysql</command> parser not to erroneously
- interpret ‘<literal>;</literal>’ character within
+ interpret <quote><literal>;</literal></quote> character within
<literal>/* ... */</literal> comment as statement terminator.
</para>
</listitem>
Modified: trunk/refman-4.1/optimization.xml
===================================================================
--- trunk/refman-4.1/optimization.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/optimization.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 949 bytes
@@ -3326,8 +3326,8 @@
that are used in round-robin fashion, so you you can use
this feature to spread the load across several directories.
Paths should be separated by colon characters
- (‘<literal>:</literal>’) on Unix and semicolon
- characters (‘<literal>;</literal>’) on Windows,
+ (<quote><literal>:</literal></quote>) on Unix and semicolon
+ characters (<quote><literal>;</literal></quote>) on Windows,
NetWare, and OS/2. The paths should be for directories in
filesystems that are located on different
<emphasis>physical</emphasis> disks, not different
Modified: trunk/refman-4.1/replication.xml
===================================================================
--- trunk/refman-4.1/replication.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/replication.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 3, Lines Added: 5, Lines Deleted: 5; 1961 bytes
@@ -3114,7 +3114,7 @@
<para>
If you use this option on the command line and the
- ‘<literal>></literal>’ character is special to
+ <quote><literal>></literal></quote> character is special to
your command interpreter, quote the option value. For example:
</para>
@@ -3175,8 +3175,8 @@
Tells the slave thread to restrict replication to statements
where any of the updated tables match the specified database
and table name patterns. Patterns can contain the
- ‘<literal>%</literal>’ and
- ‘<literal>_</literal>’ wildcard characters, which
+ <quote><literal>%</literal></quote> and
+ <quote><literal>_</literal></quote> wildcard characters, which
have the same meaning as for the <literal>LIKE</literal>
pattern-matching operator. To specify more than one table, use
this option multiple times, once for each table. This works
@@ -3208,8 +3208,8 @@
example, to replicate all tables of a database that is named
<literal>my_own%db</literal>, but not replicate tables from
the <literal>my1ownAABCdb</literal> database, you should
- escape the ‘<literal>_</literal>’ and
- ‘<literal>%</literal>’ characters like this:
+ escape the <quote><literal>_</literal></quote> and
+ <quote><literal>%</literal></quote> characters like this:
<option>--replicate-wild-do-table=my\_own\%db</option>. If
you're using the option on the command line, you might need to
double the backslashes or quote the option value, depending on
Modified: trunk/refman-4.1/se-innodb.xml
===================================================================
--- trunk/refman-4.1/se-innodb.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/se-innodb.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 2, Lines Added: 4, Lines Deleted: 4; 1804 bytes
@@ -296,7 +296,7 @@
<literal>innodb_data_file_path</literal> should be a list of one
or more data file specifications. If you name more than one data
file, separate them by semicolon
- (‘<literal>;</literal>’) characters:
+ (<quote><literal>;</literal></quote>) characters:
</para>
<programlisting>
@@ -7596,17 +7596,17 @@
With <literal>innodb_table_monitor</literal> you see a table
whose name is <filename>#sql-...</filename>. Starting from MySQL
4.0.6, you can perform SQL statements also on tables whose name
- contains the character ‘<literal>#</literal>’ if you
+ contains the character <quote><literal>#</literal></quote> if you
enclose the name within backticks. Thus, you can drop such an
orphaned table like any other orphaned table using the method
described earlier. Note that to copy or rename a file in the
Unix shell, you need to put the file name in double quotes if
- the file name contains ‘<literal>#</literal>’.
+ the file name contains <quote><literal>#</literal></quote>.
</para>
<para>
Older MySQL versions did not allow accessing any table with a
- name containing ‘<literal>#</literal>’. The solution
+ name containing <quote><literal>#</literal></quote>. The solution
in older MySQL versions is to use a special
<literal>InnoDB</literal> mechanism available starting from
MySQL 3.23.48. When you have an orphaned table
Modified: trunk/refman-4.1/sql-syntax.xml
===================================================================
--- trunk/refman-4.1/sql-syntax.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/sql-syntax.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 17, Lines Added: 28, Lines Deleted: 28; 8697 bytes
@@ -5711,8 +5711,8 @@
<listitem>
<para>
Interpret occurrences of tab, newline, or
- ‘<literal>\</literal>’ preceded by
- ‘<literal>\</literal>’ as literal characters
+ <quote><literal>\</literal></quote> preceded by
+ <quote><literal>\</literal></quote> as literal characters
that are part of field values.
</para>
</listitem>
@@ -5740,8 +5740,8 @@
<listitem>
<para>
- Use ‘<literal>\</literal>’ to escape instances
- of tab, newline, or ‘<literal>\</literal>’ that
+ Use <quote><literal>\</literal></quote> to escape instances
+ of tab, newline, or <quote><literal>\</literal></quote> that
occur within field values.
</para>
</listitem>
@@ -6032,7 +6032,7 @@
<para>
ASCII <literal>0</literal> (what is actually written
following the escape character is ASCII
- ‘<literal>0</literal>’, not a zero-valued byte)
+ <quote><literal>0</literal></quote>, not a zero-valued byte)
</para>
</listitem>
@@ -6054,7 +6054,7 @@
Some two-character sequences that are exceptions, where the
first character is the escape character. These sequences are
shown in the following table (using
- ‘<literal>\</literal>’ for the escape character).
+ <quote><literal>\</literal></quote> for the escape character).
The rules for <literal>NULL</literal> handling are described
later in this section.
</para>
@@ -6162,7 +6162,7 @@
<para>
For more information about
- ‘<literal>\</literal>’-escape syntax, see
+ <quote><literal>\</literal></quote>-escape syntax, see
<xref linkend="literals"/>.
</para>
@@ -6253,7 +6253,7 @@
output, and a field value of <literal>\N</literal> is read
as <literal>NULL</literal> for input (assuming that the
<literal>ESCAPED BY</literal> character is
- ‘<literal>\</literal>’).
+ <quote><literal>\</literal></quote>).
</para>
</listitem>
@@ -7354,7 +7354,7 @@
<para>
ASCII <literal>NUL</literal> (the zero-valued byte; what
is actually written following the escape character is
- ASCII ‘<literal>0</literal>’, not a
+ ASCII <quote><literal>0</literal></quote>, not a
zero-valued byte)
</para>
</listitem>
@@ -10138,8 +10138,8 @@
<para>
<replaceable>col_name</replaceable> can be a column name, or a
- string containing the SQL ‘<literal>%</literal>’ and
- ‘<literal>_</literal>’ wildcard characters to obtain
+ string containing the SQL <quote><literal>%</literal></quote> and
+ <quote><literal>_</literal></quote> wildcard characters to obtain
output only for the columns with names matching the string.
There is no need to enclose the string within quotes unless it
contains spaces or other special characters.
@@ -12200,14 +12200,14 @@
<note>
<para>
- the ‘<literal>_</literal>’ and
- ‘<literal>%</literal>’ wildcards are allowed
+ the <quote><literal>_</literal></quote> and
+ <quote><literal>%</literal></quote> wildcards are allowed
when specifying database names in <literal>GRANT</literal>
statements that grant privileges at the global or database
levels. This means, for example, that if you want to use a
- ‘<literal>_</literal>’ character as part of a
+ <quote><literal>_</literal></quote> character as part of a
database name, you should specify it as
- ‘<literal>\_</literal>’ in the
+ <quote><literal>\_</literal></quote> in the
<literal>GRANT</literal> statement, to prevent the user from
being able to access additional databases matching the
wildcard pattern; for example, <literal>GRANT ... ON
@@ -12225,10 +12225,10 @@
unquoted identifier, you need not quote it. However, quotes
are necessary to specify a
<replaceable>user_name</replaceable> string containing special
- characters (such as ‘<literal>-</literal>’), or a
+ characters (such as <quote><literal>-</literal></quote>), or a
<replaceable>host_name</replaceable> string containing special
characters or wildcard characters (such as
- ‘<literal>%</literal>’); for example,
+ <quote><literal>%</literal></quote>); for example,
<literal>'test-user'@'test-hostname'</literal>. Quote the
username and hostname separately.
</para>
@@ -12264,9 +12264,9 @@
<para>
When specifying quoted values, quote database, table, and
column names as identifiers, using backticks
- (‘<literal>`</literal>’). Quote hostnames,
+ (<quote><literal>`</literal></quote>). Quote hostnames,
usernames, and passwords as strings, using single quotes
- (‘<literal>'</literal>’).
+ (<quote><literal>'</literal></quote>).
</para>
<warning>
@@ -15155,8 +15155,8 @@
'<replaceable>pattern</replaceable>'</literal> part,
<literal>'<replaceable>pattern</replaceable>'</literal> is a
string that can contain the SQL
- ‘<literal>%</literal>’ and
- ‘<literal>_</literal>’ wildcard characters. The
+ <quote><literal>%</literal></quote> and
+ <quote><literal>_</literal></quote> wildcard characters. The
pattern is useful for restricting statement output to matching
values.
</para>
@@ -16170,7 +16170,7 @@
<para>
How the column is sorted in the index. In MySQL, this can
- have values ‘<literal>A</literal>’ (Ascending)
+ have values <quote><literal>A</literal></quote> (Ascending)
or <literal>NULL</literal> (Not sorted).
</para>
</listitem>
@@ -17392,7 +17392,7 @@
<para>
To get a list of variables whose name match a pattern, use the
- ‘<literal>%</literal>’ wildcard character in a
+ <quote><literal>%</literal></quote> wildcard character in a
<literal>LIKE</literal> clause:
</para>
@@ -17404,9 +17404,9 @@
<para>
Wildcard characters can be used in any position within the
pattern to be matched. Strictly speaking, because
- ‘<literal>_</literal>’ is a wildcard that matches
+ <quote><literal>_</literal></quote> is a wildcard that matches
any single character, you should escape it as
- ‘<literal>\_</literal>’ to match it literally. In
+ <quote><literal>\_</literal></quote> to match it literally. In
practice, this is rarely necessary.
</para>
@@ -20360,10 +20360,10 @@
is either a string literal or a user variable that contains
the text of the statement. The text must represent a single
SQL statement, not multiple statements. Within the statement,
- ‘<literal>?</literal>’ characters can be used as
+ <quote><literal>?</literal></quote> characters can be used as
parameter markers to indicate where data values are to be
bound to the query later when you execute it. The
- ‘<literal>?</literal>’ characters should not be
+ <quote><literal>?</literal></quote> characters should not be
enclosed within quotes, even if you intend to bind them to
string values. Parameter markers can be used only where data
values should appear, not for SQL keywords, identifiers, and
@@ -20546,7 +20546,7 @@
<para>
SQL syntax for prepared statements does not support
multi-statements (that is, multiple statements within a single
- string separated by ‘<literal>;</literal>’
+ string separated by <quote><literal>;</literal></quote>
characters).
</para>
Modified: trunk/refman-4.1/tutorial.xml
===================================================================
--- trunk/refman-4.1/tutorial.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/tutorial.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 15, Lines Added: 38, Lines Deleted: 38; 9192 bytes
@@ -435,18 +435,18 @@
<row>
<entry><literal>'></literal></entry>
<entry>Waiting for next line, waiting for completion of a string that began
- with a single quote (‘<literal>'</literal>’).</entry>
+ with a single quote (<quote><literal>'</literal></quote>).</entry>
</row>
<row>
<entry><literal>"></literal></entry>
<entry>Waiting for next line, waiting for completion of a string that began
- with a double quote (‘<literal>"</literal>’).</entry>
+ with a double quote (<quote><literal>"</literal></quote>).</entry>
</row>
<row>
<entry><literal>`></literal></entry>
<entry>Waiting for next line, waiting for completion of an identifier that
began with a backtick
- (‘<literal>`</literal>’).</entry>
+ (<quote><literal>`</literal></quote>).</entry>
</row>
<row>
<entry><literal>/*></literal></entry>
@@ -499,15 +499,15 @@
The <literal>'></literal> and <literal>"></literal> prompts
occur during string collection (another way of saying that MySQL
is waiting for completion of a string). In MySQL, you can write
- strings surrounded by either ‘<literal>'</literal>’ or
- ‘<literal>"</literal>’ characters (for example,
+ strings surrounded by either <quote><literal>'</literal></quote> or
+ <quote><literal>"</literal></quote> characters (for example,
<literal>'hello'</literal> or <literal>"goodbye"</literal>), and
<command>mysql</command> lets you enter strings that span multiple
lines. When you see a <literal>'></literal> or
<literal>"></literal> prompt, it means that you have entered a
line containing a string that begins with a
- ‘<literal>'</literal>’ or
- ‘<literal>"</literal>’ quote character, but have not
+ <quote><literal>'</literal></quote> or
+ <quote><literal>"</literal></quote> quote character, but have not
yet entered the matching quote that terminates the string. This
often indicates that you have inadvertently left out a quote
character. For example:
@@ -2060,8 +2060,8 @@
<para>
SQL pattern matching allows you to use
- ‘<literal>_</literal>’ to match any single
- character and ‘<literal>%</literal>’ to match an
+ <quote><literal>_</literal></quote> to match any single
+ character and <quote><literal>%</literal></quote> to match an
arbitrary number of characters (including zero characters). In
MySQL, SQL patterns are case-insensitive by default. Some
examples are shown here. Note that you do not use
@@ -2072,7 +2072,7 @@
<para>
To find names beginning with
- ‘<literal>b</literal>’:
+ <quote><literal>b</literal></quote>:
</para>
<programlisting>
@@ -2086,7 +2086,7 @@
</programlisting>
<para>
- To find names ending with ‘<literal>fy</literal>’:
+ To find names ending with <quote><literal>fy</literal></quote>:
</para>
<programlisting>
@@ -2100,7 +2100,7 @@
</programlisting>
<para>
- To find names containing a ‘<literal>w</literal>’:
+ To find names containing a <quote><literal>w</literal></quote>:
</para>
<programlisting>
@@ -2116,7 +2116,7 @@
<para>
To find names containing exactly five characters, use five
- instances of the ‘<literal>_</literal>’ pattern
+ instances of the <quote><literal>_</literal></quote> pattern
character:
</para>
@@ -2147,34 +2147,34 @@
<listitem>
<para>
- ‘<literal>.</literal>’ matches any single
+ <quote><literal>.</literal></quote> matches any single
character.
</para>
</listitem>
<listitem>
<para>
- A character class ‘<literal>[...]</literal>’
+ A character class <quote><literal>[...]</literal></quote>
matches any character within the brackets. For example,
- ‘<literal>[abc]</literal>’ matches
- ‘<literal>a</literal>’,
- ‘<literal>b</literal>’, or
- ‘<literal>c</literal>’. To name a range of
+ <quote><literal>[abc]</literal></quote> matches
+ <quote><literal>a</literal></quote>,
+ <quote><literal>b</literal></quote>, or
+ <quote><literal>c</literal></quote>. To name a range of
characters, use a dash.
- ‘<literal>[a-z]</literal>’ matches any letter,
- whereas ‘<literal>[0-9]</literal>’ matches any
+ <quote><literal>[a-z]</literal></quote> matches any letter,
+ whereas <quote><literal>[0-9]</literal></quote> matches any
digit.
</para>
</listitem>
<listitem>
<para>
- ‘<literal>*</literal>’ matches zero or more
+ <quote><literal>*</literal></quote> matches zero or more
instances of the thing preceding it. For example,
- ‘<literal>x*</literal>’ matches any number of
- ‘<literal>x</literal>’ characters,
- ‘<literal>[0-9]*</literal>’ matches any number
- of digits, and ‘<literal>.*</literal>’ matches
+ <quote><literal>x*</literal></quote> matches any number of
+ <quote><literal>x</literal></quote> characters,
+ <quote><literal>[0-9]*</literal></quote> matches any number
+ of digits, and <quote><literal>.*</literal></quote> matches
any number of anything.
</para>
</listitem>
@@ -2193,8 +2193,8 @@
<para>
To anchor a pattern so that it must match the beginning or
end of the value being tested, use
- ‘<literal>^</literal>’ at the beginning or
- ‘<literal>$</literal>’ at the end of the
+ <quote><literal>^</literal></quote> at the beginning or
+ <quote><literal>$</literal></quote> at the end of the
pattern.
</para>
</listitem>
@@ -2209,8 +2209,8 @@
<para>
To find names beginning with
- ‘<literal>b</literal>’, use
- ‘<literal>^</literal>’ to match the beginning of
+ <quote><literal>b</literal></quote>, use
+ <quote><literal>^</literal></quote> to match the beginning of
the name:
</para>
@@ -2228,7 +2228,7 @@
Prior to MySQL 3.23.4, <literal>REGEXP</literal> is case
sensitive, and the previous query will return no rows. In this
case, to match either lowercase or uppercase
- ‘<literal>b</literal>’, use this query instead:
+ <quote><literal>b</literal></quote>, use this query instead:
</para>
<programlisting>
@@ -2240,7 +2240,7 @@
<literal>REGEXP</literal> comparison to be case sensitive, use
the <literal>BINARY</literal> keyword to make one of the
strings a binary string. This query matches only lowercase
- ‘<literal>b</literal>’ at the beginning of a name:
+ <quote><literal>b</literal></quote> at the beginning of a name:
</para>
<programlisting>
@@ -2248,8 +2248,8 @@
</programlisting>
<para>
- To find names ending with ‘<literal>fy</literal>’,
- use ‘<literal>$</literal>’ to match the end of the
+ To find names ending with <quote><literal>fy</literal></quote>,
+ use <quote><literal>$</literal></quote> to match the end of the
name:
</para>
@@ -2264,7 +2264,7 @@
</programlisting>
<para>
- To find names containing a ‘<literal>w</literal>’,
+ To find names containing a <quote><literal>w</literal></quote>,
use this query:
</para>
@@ -2289,10 +2289,10 @@
<para>
To find names containing exactly five characters, use
- ‘<literal>^</literal>’ and
- ‘<literal>$</literal>’ to match the beginning and
+ <quote><literal>^</literal></quote> and
+ <quote><literal>$</literal></quote> to match the beginning and
end of the name, and five instances of
- ‘<literal>.</literal>’ in between:
+ <quote><literal>.</literal></quote> in between:
</para>
<programlisting>
Modified: trunk/refman-4.1/using-mysql-programs.xml
===================================================================
--- trunk/refman-4.1/using-mysql-programs.xml 2007-10-08 08:20:46 UTC (rev 8011)
+++ trunk/refman-4.1/using-mysql-programs.xml 2007-10-08 09:42:49 UTC (rev 8012)
Changed blocks: 7, Lines Added: 21, Lines Deleted: 21; 5293 bytes
@@ -251,8 +251,8 @@
<para>
Arguments that begin with a single or double dash
- (‘<literal>-</literal>’,
- ‘<literal>--</literal>’) are option arguments. Options
+ (<quote><literal>-</literal></quote>,
+ <quote><literal>--</literal></quote>) are option arguments. Options
typically specify the type of connection a program should make to
the server or affect its operational mode. Option syntax is
described in <xref linkend="program-options"/>.
@@ -504,7 +504,7 @@
<listitem>
<para>
For a long option that takes a value, separate the option
- name and the value by an ‘<literal>=</literal>’
+ name and the value by an <quote><literal>=</literal></quote>
sign. For a short option that takes a value, the option
value can immediately follow the option letter, or there can
be a space between: <option>-hlocalhost</option> and
@@ -979,9 +979,9 @@
</para>
<para>
- Comment lines start with ‘<literal>#</literal>’
- or ‘<literal>;</literal>’. As of MySQL 4.0.14, a
- ‘<literal>#</literal>’ comment can start in the
+ Comment lines start with <quote><literal>#</literal></quote>
+ or <quote><literal>;</literal></quote>. As of MySQL 4.0.14, a
+ <quote><literal>#</literal></quote> comment can start in the
middle of a line as well.
</para>
</listitem>
@@ -1021,11 +1021,11 @@
This is equivalent to
<option>--<replaceable>opt_name</replaceable>=<replaceable>value</replaceable></option>
on the command line. In an option file, you can have spaces
- around the ‘<literal>=</literal>’ character,
+ around the <quote><literal>=</literal></quote> character,
something that is not true on the command line. As of MySQL
4.0.16, you can enclose the value within double quotes or
single quotes. This is useful if the value contains a
- ‘<literal>#</literal>’ comment character or
+ <quote><literal>#</literal></quote> comment character or
whitespace.
</para>
</listitem>
@@ -1041,7 +1041,7 @@
to the given value. This is equivalent to
<option>--set-variable=<replaceable>var_name</replaceable>=<replaceable>value</replaceable></option>
on the command line. Spaces are allowed around the first
- ‘<literal>=</literal>’ character but not around
+ <quote><literal>=</literal></quote> character but not around
the second. This syntax is deprecated as of MySQL 4.0. See
<xref linkend="program-variables"/>, for more information on
setting program variables.
@@ -1067,23 +1067,23 @@
<para>
Leading and trailing blanks are automatically deleted from
option names and values. You may use the escape sequences
- ‘<literal>\b</literal>’,
- ‘<literal>\t</literal>’,
- ‘<literal>\n</literal>’,
- ‘<literal>\r</literal>’,
- ‘<literal>\\</literal>’, and
- ‘<literal>\s</literal>’ in option values to
+ <quote><literal>\b</literal></quote>,
+ <quote><literal>\t</literal></quote>,
+ <quote><literal>\n</literal></quote>,
+ <quote><literal>\r</literal></quote>,
+ <quote><literal>\\</literal></quote>, and
+ <quote><literal>\s</literal></quote> in option values to
represent the backspace, tab, newline, carriage return,
backslash, and space characters.
</para>
<para>
- Because the ‘<literal>\\</literal>’ escape sequence
+ Because the <quote><literal>\\</literal></quote> escape sequence
represents a single backslash, you must write each
- ‘<literal>\</literal>’ as
- ‘<literal>\\</literal>’. Alternatively, you can
- specify the value using ‘<literal>/</literal>’
- rather than ‘<literal>\</literal>’ as the pathname
+ <quote><literal>\</literal></quote> as
+ <quote><literal>\\</literal></quote>. Alternatively, you can
+ specify the value using <quote><literal>/</literal></quote>
+ rather than <quote><literal>\</literal></quote> as the pathname
separator.
</para>
@@ -1299,7 +1299,7 @@
<option>--print-defaults</option> may be used immediately after
<option>--defaults-file</option> or
<option>--defaults-extra-file</option>. Also, you should avoid
- the use of the ‘<literal>~</literal>’ shell
+ the use of the <quote><literal>~</literal></quote> shell
metacharacter when specifying filenames because it might not be
interpreted as you expect.
</para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r8012 - trunk/refman-4.1 | jon | 8 Oct |
