Below is the list of changes that have just been committed into a local
mysqldoc repository of paul. When paul does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html
ChangeSet
1.3137 05/07/26 21:20:45 paul@stripped +3 -0
Kill Texinfo quotes.
refman/introduction.xml
1.18 05/07/26 21:20:43 paul@stripped +134 -123
Kill Texinfo quotes.
refman-5.0/introduction.xml
1.18 05/07/26 21:20:43 paul@stripped +128 -118
Kill Texinfo quotes.
refman-4.1/introduction.xml
1.19 05/07/26 21:20:43 paul@stripped +130 -120
Kill Texinfo quotes.
# This is a BitKeeper patch. What follows are the unified diffs for the
# set of deltas contained in the patch. The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User: paul
# Host: frost.snake.net
# Root: /Volumes/frost2/MySQL/bk/mysqldoc
--- 1.18/refman-4.1/introduction.xml 2005-07-25 21:15:20 -05:00
+++ 1.19/refman-4.1/introduction.xml 2005-07-26 21:20:43 -05:00
@@ -135,9 +135,10 @@
</para>
<para>
- Reports of errors (often called ``bugs''), as well as questions and
- comments, should be sent to <ulink url="http://bugs.mysql.com"/>.
- See <xref linkend="bug-reports"/>.
+ Reports of errors (often called <quote>bugs</quote>), as well as
+ questions and comments, should be sent to
+ <ulink url="http://bugs.mysql.com"/>. See
+ <xref linkend="bug-reports"/>.
</para>
<para>
@@ -240,9 +241,9 @@
<para>
This manual was initially written by David Axmark and Michael
- ``Monty'' Widenius. It is maintained by the MySQL Documentation
- Team, consisting of Paul DuBois, Stefan Hinz, Mike Hillyer, and
- Jon Stephens. For the many other contributors, see
+ <quote>Monty</quote> Widenius. It is maintained by the MySQL
+ Documentation Team, consisting of Paul DuBois, Stefan Hinz, Mike
+ Hillyer, and Jon Stephens. For the many other contributors, see
<xref linkend="credits"/>.
</para>
@@ -292,9 +293,9 @@
<para>
<literal>Text in this style</literal> is used for SQL
statements; database, table, and column names; C and Perl
- code; and environment variables. Example: ``To reload the
+ code; and environment variables. Example: <quote>To reload the
grant tables, use the <literal>FLUSH PRIVILEGES</literal>
- statement.''
+ statement.</quote>
</para>
<!-- @item -->
@@ -314,16 +315,16 @@
<listitem>
<para>
- Filenames and directory names are written like this: ``The
- global <filename>my.cnf</filename> file is located in the
- <filename>/etc</filename> directory.''
+ Filenames and directory names are written like this:
+ <quote>The global <filename>my.cnf</filename> file is located
+ in the <filename>/etc</filename> directory.</quote>
</para>
</listitem>
<listitem>
<para>
- Character sequences are written like this: ``To specify a
- wildcard, use the '<literal>%</literal>' character.''
+ Character sequences are written like this: <quote>To specify a
+ wildcard, use the '<literal>%</literal>' character.</quote>
</para>
</listitem>
@@ -357,8 +358,8 @@
</programlisting>
<para>
- The ``shell'' is your command interpreter. On Unix, this is
- typically a program such as <command>sh</command> or
+ The <quote>shell</quote> is your command interpreter. On Unix,
+ this is typically a program such as <command>sh</command> or
<command>csh</command>. On Windows, the equivalent program is
<command>command.com</command> or <command>cmd.exe</command>,
typically run in a console window.
@@ -494,7 +495,7 @@
<para>
MySQL AB is the company of the MySQL founders and main developers.
MySQL AB was originally established in Sweden by David Axmark,
- Allan Larsson, and Michael ``Monty'' Widenius.
+ Allan Larsson, and Michael <quote>Monty</quote> Widenius.
</para>
<para>
@@ -606,10 +607,11 @@
</para>
<para>
- By the way, the ``AB'' part of the company name is the acronym for
- the Swedish ``aktiebolag,'' or ``stock company.'' It translates to
- ``MySQL, Inc.'' In fact, MySQL, Inc. and MySQL GmbH are examples
- of MySQL AB subsidiaries. They are located in the US and Germany,
+ By the way, the <quote>AB</quote> part of the company name is the
+ acronym for the Swedish <quote>aktiebolag,</quote> or <quote>stock
+ company.</quote> It translates to <quote>MySQL, Inc.</quote> In
+ fact, MySQL, Inc. and MySQL GmbH are examples of MySQL AB
+ subsidiaries. They are located in the US and Germany,
respectively.
</para>
@@ -675,16 +677,17 @@
A relational database stores data in separate tables rather
than putting all the data in one big storeroom. This adds
- speed and flexibility. The SQL part of ``MySQL'' stands for
- ``Structured Query Language.'' SQL is the most common
- standardized language used to access databases and is defined
- by the ANSI/ISO SQL Standard. The SQL standard has been
- evolving since 1986 and several versions exist. In this
- manual, ``SQL-92'' refers to the standard released in 1992,
- ``SQL:1999'' refers to the standard released in 1999, and
- ``SQL:2003'' refers to the current version of the standard. We
- use the phrase ``the SQL standard'' to mean the current
- version of the SQL Standard at any time.
+ speed and flexibility. The SQL part of <quote>MySQL</quote>
+ stands for <quote>Structured Query Language.</quote> SQL is
+ the most common standardized language used to access databases
+ and is defined by the ANSI/ISO SQL Standard. The SQL standard
+ has been evolving since 1986 and several versions exist. In
+ this manual, <quote>SQL-92</quote> refers to the standard
+ released in 1992, <quote>SQL:1999</quote> refers to the
+ standard released in 1999, and <quote>SQL:2003</quote> refers
+ to the current version of the standard. We use the phrase
+ <quote>the SQL standard</quote> to mean the current version of
+ the SQL Standard at any time.
</para>
</listitem>
@@ -801,9 +804,10 @@
</indexterm>
<para>
- The official way to pronounce ``MySQL'' is ``My Ess Que Ell'' (not
- ``my sequel''), but we don't mind if you pronounce it as ``my
- sequel'' or in some other localized way.
+ The official way to pronounce <quote>MySQL</quote> is <quote>My
+ Ess Que Ell</quote> (not <quote>my sequel</quote>), but we don't
+ mind if you pronounce it as <quote>my sequel</quote> or in some
+ other localized way.
</para>
<section id="history">
@@ -850,20 +854,21 @@
<para>
The derivation of the name MySQL is not clear. Our base
directory and a large number of our libraries and tools have had
- the prefix ``my'' for well over 10 years. However, co-founder
- Monty Widenius's daughter is also named My. Which of the two
- gave its name to MySQL is still a mystery, even for us.
+ the prefix <quote>my</quote> for well over 10 years. However,
+ co-founder Monty Widenius's daughter is also named My. Which of
+ the two gave its name to MySQL is still a mystery, even for us.
</para>
<para>
- The name of the MySQL Dolphin (our logo) is ``Sakila,'' which
- was chosen by the founders of MySQL AB from a huge list of names
- suggested by users in our ``Name the Dolphin'' contest. The
- winning name was submitted by Ambrose Twebaze, an Open Source
- software developer from Swaziland, Africa. According to Ambrose,
- the feminine name Sakila has its roots in SiSwati, the local
- language of Swaziland. Sakila is also the name of a town in
- Arusha, Tanzania, near Ambrose's country of origin, Uganda.
+ The name of the MySQL Dolphin (our logo) is
+ <quote>Sakila,</quote> which was chosen by the founders of MySQL
+ AB from a huge list of names suggested by users in our
+ <quote>Name the Dolphin</quote> contest. The winning name was
+ submitted by Ambrose Twebaze, an Open Source software developer
+ from Swaziland, Africa. According to Ambrose, the feminine name
+ Sakila has its roots in SiSwati, the local language of
+ Swaziland. Sakila is also the name of a town in Arusha,
+ Tanzania, near Ambrose's country of origin, Uganda.
</para>
</section>
@@ -1223,7 +1228,8 @@
can use MS Access to connect to your MySQL server.
Clients can be run on Windows or Unix. MyODBC source
is available. All ODBC 2.5 functions are supported, as
- are many others. See <xref linkend="mysql-connectors"/>.
+ are many others. See
+ <xref linkend="mysql-connectors"/>.
</para>
</listitem>
@@ -1335,14 +1341,14 @@
</indexterm>
<para>
- This section addresses the questions, ``<emphasis>How stable is
- MySQL Server?</emphasis>'' and, ``<emphasis>Can I depend on
- MySQL Server in this project?</emphasis>'' We will try to
- clarify these issues and answer some important questions that
- concern many potential users. The information in this section is
- based on data gathered from the mailing lists, which are very
- active in identifying problems as well as reporting types of
- use.
+ This section addresses the questions, <quote><emphasis>How
+ stable is MySQL Server?</emphasis></quote> and,
+ <quote><emphasis>Can I depend on MySQL Server in this
+ project?</emphasis></quote> We will try to clarify these issues
+ and answer some important questions that concern many potential
+ users. The information in this section is based on data gathered
+ from the mailing lists, which are very active in identifying
+ problems as well as reporting types of use.
</para>
<para>
@@ -1359,14 +1365,14 @@
<para>
Each release of the MySQL Server has been usable. Problems have
- occurred only when users try code from the ``gray zones.''
- Naturally, new users don't know what the gray zones are; this
- section therefore attempts to document those areas that are
- currently known. The descriptions mostly deal with Version 3.23,
- 4.0 and 4.1 of MySQL Server. All known and reported bugs are
- fixed in the latest version, with the exception of those listed
- in the bugs section, which are design-related. See
- <xref linkend="bugs"/>.
+ occurred only when users try code from the <quote>gray
+ zones.</quote> Naturally, new users don't know what the gray
+ zones are; this section therefore attempts to document those
+ areas that are currently known. The descriptions mostly deal
+ with Version 3.23, 4.0 and 4.1 of MySQL Server. All known and
+ reported bugs are fixed in the latest version, with the
+ exception of those listed in the bugs section, which are
+ design-related. See <xref linkend="bugs"/>.
</para>
<para>
@@ -1770,11 +1776,11 @@
using two-digit values (which are ambiguous) rather than
four-digit values. This problem may be compounded by
applications that use values such as <literal>00</literal> or
- <literal>99</literal> as ``missing'' value indicators.
- Unfortunately, these problems may be difficult to fix because
- different applications may be written by different programmers,
- each of whom may use a different set of conventions and
- date-handling functions.
+ <literal>99</literal> as <quote>missing</quote> value
+ indicators. Unfortunately, these problems may be difficult to
+ fix because different applications may be written by different
+ programmers, each of whom may use a different set of conventions
+ and date-handling functions.
</para>
<para>
@@ -2225,11 +2231,12 @@
<listitem>
<para>
- A ``subquery'' is a <literal>SELECT</literal>
- statement nested within another statement. A
- ``derived table'' (an unnamed view) is a subquery in
- the <literal>FROM</literal> clause of another
- statement. See <xref linkend="subqueries"/>.
+ A <quote>subquery</quote> is a
+ <literal>SELECT</literal> statement nested within
+ another statement. A <quote>derived table</quote>
+ (an unnamed view) is a subquery in the
+ <literal>FROM</literal> clause of another statement.
+ See <xref linkend="subqueries"/>.
</para>
</listitem>
@@ -3010,13 +3017,13 @@
server is installed (including the platform type and version
number). This is highly relevant information, and in 99 cases
out of 100, the bug report is useless without it. Very often
- we get questions like, ``Why doesn't this work for me?'' Then
- we find that the feature requested wasn't implemented in that
- MySQL version, or that a bug described in a report has been
- fixed in newer MySQL versions. Sometimes the error is
- platform-dependent; in such cases, it is next to impossible
- for us to fix anything without knowing the operating system
- and the version number of the platform.
+ we get questions like, <quote>Why doesn't this work for
+ me?</quote> Then we find that the feature requested wasn't
+ implemented in that MySQL version, or that a bug described in
+ a report has been fixed in newer MySQL versions. Sometimes the
+ error is platform-dependent; in such cases, it is next to
+ impossible for us to fix anything without knowing the
+ operating system and the version number of the platform.
</para>
<para>
@@ -3102,9 +3109,9 @@
The operating system name and version. If you work with
Windows, you can usually get the name and version number
by double-clicking your My Computer icon and pulling down
- the ``Help/About Windows'' menu. For most Unix-like
- operating systems, you can get this information by
- executing the command <literal>uname -a</literal>.
+ the <quote>Help/About Windows</quote> menu. For most
+ Unix-like operating systems, you can get this information
+ by executing the command <literal>uname -a</literal>.
</para>
</listitem>
@@ -3687,11 +3694,12 @@
<para>
The SQL standard has been evolving since 1986 and several versions
- exist. In this manual, ``SQL-92'' refers to the standard released
- in 1992, ``SQL:1999'' refers to the standard released in 1999, and
- ``SQL:2003'' refers to the current version of the standard. We use
- the phrase ``the SQL standard'' to mean the current version of the
- SQL Standard at any given time.
+ exist. In this manual, <quote>SQL-92</quote> refers to the
+ standard released in 1992, <quote>SQL:1999</quote> refers to the
+ standard released in 1999, and <quote>SQL:2003</quote> refers to
+ the current version of the standard. We use the phrase <quote>the
+ SQL standard</quote> to mean the current version of the SQL
+ Standard at any given time.
</para>
<para>
@@ -4486,10 +4494,11 @@
<para>
MySQL 4.1 supports subqueries and derived tables. A
- ``subquery'' is a <literal>SELECT</literal> statement nested
- within another statement. A ``derived table'' (an unnamed
- view) is a subquery in the <literal>FROM</literal> clause of
- another statement. See <xref linkend="subqueries"/>.
+ <quote>subquery</quote> is a <literal>SELECT</literal>
+ statement nested within another statement. A <quote>derived
+ table</quote> (an unnamed view) is a subquery in the
+ <literal>FROM</literal> clause of another statement. See
+ <xref linkend="subqueries"/>.
</para>
<para>
@@ -4586,11 +4595,11 @@
<para>
The other non-transactional storage engines in MySQL Server
(such as <literal>MyISAM</literal>) follow a different
- paradigm for data integrity called ``atomic operations.'' In
- transactional terms, <literal>MyISAM</literal> tables
- effectively always operate in <literal>AUTOCOMMIT=1</literal>
- mode. Atomic operations often offer comparable integrity with
- higher performance.
+ paradigm for data integrity called <quote>atomic
+ operations.</quote> In transactional terms,
+ <literal>MyISAM</literal> tables effectively always operate in
+ <literal>AUTOCOMMIT=1</literal> mode. Atomic operations often
+ offer comparable integrity with higher performance.
</para>
<para>
@@ -4701,12 +4710,13 @@
</para>
<para>
- ``Atomic,'' in the sense that we mean it, is nothing magical.
- It only means that you can be sure that while each specific
- update is running, no other user can interfere with it, and
- there can never be an automatic rollback (which can happen
- with transactional tables if you are not very careful). MySQL
- Server also guarantees that there are no dirty reads.
+ <quote>Atomic,</quote> in the sense that we mean it, is
+ nothing magical. It only means that you can be sure that while
+ each specific update is running, no other user can interfere
+ with it, and there can never be an automatic rollback (which
+ can happen with transactional tables if you are not very
+ careful). MySQL Server also guarantees that there are no dirty
+ reads.
</para>
<para>
@@ -4802,11 +4812,11 @@
compared to the original row. The test for changed data is
done with the <literal>WHERE</literal> clause in the
<literal>UPDATE</literal> statement. If the record wasn't
- updated, we give the client a message: ``Some of the data
- you have changed has been changed by another user.'' Then
- we show the old row versus the new row in a window so that
- the user can decide which version of the customer record
- to use.
+ updated, we give the client a message: <quote>Some of the
+ data you have changed has been changed by another
+ user.</quote> Then we show the old row versus the new row
+ in a window so that the user can decide which version of
+ the customer record to use.
</para>
<para>
@@ -5202,9 +5212,9 @@
</programlisting>
<para>
- You can also edit the command file ``in place'' to change the
- '<literal>--</literal>' comments to '<literal>#</literal>'
- comments:
+ You can also edit the command file <quote>in place</quote> to
+ change the '<literal>--</literal>' comments to
+ '<literal>#</literal>' comments:
</para>
<programlisting>
@@ -5348,11 +5358,11 @@
<para>
Through version 4.1, MySQL is forgiving of illegal or improper
data values and coerces them to legal values for data entry.
- If you insert an ``incorrect'' value into a column, such as a
- <literal>NULL</literal> into a <literal>NOT NULL</literal>
- column or a too-large numeric value into a numeric column,
- MySQL sets the column to the ``best possible value'' instead
- of producing an error:
+ If you insert an <quote>incorrect</quote> value into a column,
+ such as a <literal>NULL</literal> into a <literal>NOT
+ NULL</literal> column or a too-large numeric value into a
+ numeric column, MySQL sets the column to the <quote>best
+ possible value</quote> instead of producing an error:
</para>
<itemizedlist>
@@ -5407,8 +5417,8 @@
implicit default value for the column data type. In
general, this is <literal>0</literal> for numeric types,
the empty string (<literal>''</literal>) for string types,
- and the ``zero'' value for date and time types. Implicit
- default values are discussed in
+ and the <quote>zero</quote> value for date and time types.
+ Implicit default values are discussed in
<xref linkend="create-table"/>.
</para>
</listitem>
@@ -5432,10 +5442,10 @@
can't just roll back if we encounter a problem after updating
a few rows, because the storage engine may not support
rollback. The option of terminating the statement is not that
- good; in this case, the update would be ``half done,'' which
- is probably the worst possible scenario. In this case, it's
- better to ``do the best you can'' and then continue as if
- nothing happened.
+ good; in this case, the update would be <quote>half
+ done,</quote> which is probably the worst possible scenario.
+ In this case, it's better to <quote>do the best you
+ can</quote> and then continue as if nothing happened.
</para>
</section>
--- 1.17/refman-5.0/introduction.xml 2005-07-25 21:15:21 -05:00
+++ 1.18/refman-5.0/introduction.xml 2005-07-26 21:20:43 -05:00
@@ -122,9 +122,10 @@
</para>
<para>
- Reports of errors (often called ``bugs''), as well as questions and
- comments, should be sent to <ulink url="http://bugs.mysql.com"/>.
- See <xref linkend="bug-reports"/>.
+ Reports of errors (often called <quote>bugs</quote>), as well as
+ questions and comments, should be sent to
+ <ulink url="http://bugs.mysql.com"/>. See
+ <xref linkend="bug-reports"/>.
</para>
<para>
@@ -229,9 +230,9 @@
<para>
This manual was initially written by David Axmark and Michael
- ``Monty'' Widenius. It is maintained by the MySQL Documentation
- Team, consisting of Paul DuBois, Stefan Hinz, Mike Hillyer, and
- Jon Stephens. For the many other contributors, see
+ <quote>Monty</quote> Widenius. It is maintained by the MySQL
+ Documentation Team, consisting of Paul DuBois, Stefan Hinz, Mike
+ Hillyer, and Jon Stephens. For the many other contributors, see
<xref linkend="credits"/>.
</para>
@@ -281,9 +282,9 @@
<para>
<literal>Text in this style</literal> is used for SQL
statements; database, table, and column names; C and Perl
- code; and environment variables. Example: ``To reload the
+ code; and environment variables. Example: <quote>To reload the
grant tables, use the <literal>FLUSH PRIVILEGES</literal>
- statement.''
+ statement.</quote>
</para>
<!-- @item -->
@@ -303,16 +304,16 @@
<listitem>
<para>
- Filenames and directory names are written like this: ``The
- global <filename>my.cnf</filename> file is located in the
- <filename>/etc</filename> directory.''
+ Filenames and directory names are written like this:
+ <quote>The global <filename>my.cnf</filename> file is located
+ in the <filename>/etc</filename> directory.</quote>
</para>
</listitem>
<listitem>
<para>
- Character sequences are written like this: ``To specify a
- wildcard, use the '<literal>%</literal>' character.''
+ Character sequences are written like this: <quote>To specify a
+ wildcard, use the '<literal>%</literal>' character.</quote>
</para>
</listitem>
@@ -346,8 +347,8 @@
</programlisting>
<para>
- The ``shell'' is your command interpreter. On Unix, this is
- typically a program such as <command>sh</command> or
+ The <quote>shell</quote> is your command interpreter. On Unix,
+ this is typically a program such as <command>sh</command> or
<command>csh</command>. On Windows, the equivalent program is
<command>command.com</command> or <command>cmd.exe</command>,
typically run in a console window.
@@ -483,7 +484,7 @@
<para>
MySQL AB is the company of the MySQL founders and main developers.
MySQL AB was originally established in Sweden by David Axmark,
- Allan Larsson, and Michael ``Monty'' Widenius.
+ Allan Larsson, and Michael <quote>Monty</quote> Widenius.
</para>
<para>
@@ -595,10 +596,11 @@
</para>
<para>
- By the way, the ``AB'' part of the company name is the acronym for
- the Swedish ``aktiebolag,'' or ``stock company.'' It translates to
- ``MySQL, Inc.'' In fact, MySQL, Inc. and MySQL GmbH are examples
- of MySQL AB subsidiaries. They are located in the US and Germany,
+ By the way, the <quote>AB</quote> part of the company name is the
+ acronym for the Swedish <quote>aktiebolag,</quote> or <quote>stock
+ company.</quote> It translates to <quote>MySQL, Inc.</quote> In
+ fact, MySQL, Inc. and MySQL GmbH are examples of MySQL AB
+ subsidiaries. They are located in the US and Germany,
respectively.
</para>
@@ -664,16 +666,17 @@
A relational database stores data in separate tables rather
than putting all the data in one big storeroom. This adds
- speed and flexibility. The SQL part of ``MySQL'' stands for
- ``Structured Query Language.'' SQL is the most common
- standardized language used to access databases and is defined
- by the ANSI/ISO SQL Standard. The SQL standard has been
- evolving since 1986 and several versions exist. In this
- manual, ``SQL-92'' refers to the standard released in 1992,
- ``SQL:1999'' refers to the standard released in 1999, and
- ``SQL:2003'' refers to the current version of the standard. We
- use the phrase ``the SQL standard'' to mean the current
- version of the SQL Standard at any time.
+ speed and flexibility. The SQL part of <quote>MySQL</quote>
+ stands for <quote>Structured Query Language.</quote> SQL is
+ the most common standardized language used to access databases
+ and is defined by the ANSI/ISO SQL Standard. The SQL standard
+ has been evolving since 1986 and several versions exist. In
+ this manual, <quote>SQL-92</quote> refers to the standard
+ released in 1992, <quote>SQL:1999</quote> refers to the
+ standard released in 1999, and <quote>SQL:2003</quote> refers
+ to the current version of the standard. We use the phrase
+ <quote>the SQL standard</quote> to mean the current version of
+ the SQL Standard at any time.
</para>
</listitem>
@@ -790,9 +793,10 @@
</indexterm>
<para>
- The official way to pronounce ``MySQL'' is ``My Ess Que Ell'' (not
- ``my sequel''), but we don't mind if you pronounce it as ``my
- sequel'' or in some other localized way.
+ The official way to pronounce <quote>MySQL</quote> is <quote>My
+ Ess Que Ell</quote> (not <quote>my sequel</quote>), but we don't
+ mind if you pronounce it as <quote>my sequel</quote> or in some
+ other localized way.
</para>
<section id="history">
@@ -839,20 +843,21 @@
<para>
The derivation of the name MySQL is not clear. Our base
directory and a large number of our libraries and tools have had
- the prefix ``my'' for well over 10 years. However, co-founder
- Monty Widenius's daughter is also named My. Which of the two
- gave its name to MySQL is still a mystery, even for us.
+ the prefix <quote>my</quote> for well over 10 years. However,
+ co-founder Monty Widenius's daughter is also named My. Which of
+ the two gave its name to MySQL is still a mystery, even for us.
</para>
<para>
- The name of the MySQL Dolphin (our logo) is ``Sakila,'' which
- was chosen by the founders of MySQL AB from a huge list of names
- suggested by users in our ``Name the Dolphin'' contest. The
- winning name was submitted by Ambrose Twebaze, an Open Source
- software developer from Swaziland, Africa. According to Ambrose,
- the feminine name Sakila has its roots in SiSwati, the local
- language of Swaziland. Sakila is also the name of a town in
- Arusha, Tanzania, near Ambrose's country of origin, Uganda.
+ The name of the MySQL Dolphin (our logo) is
+ <quote>Sakila,</quote> which was chosen by the founders of MySQL
+ AB from a huge list of names suggested by users in our
+ <quote>Name the Dolphin</quote> contest. The winning name was
+ submitted by Ambrose Twebaze, an Open Source software developer
+ from Swaziland, Africa. According to Ambrose, the feminine name
+ Sakila has its roots in SiSwati, the local language of
+ Swaziland. Sakila is also the name of a town in Arusha,
+ Tanzania, near Ambrose's country of origin, Uganda.
</para>
</section>
@@ -1212,7 +1217,8 @@
can use MS Access to connect to your MySQL server.
Clients can be run on Windows or Unix. MyODBC source
is available. All ODBC 2.5 functions are supported, as
- are many others. See <xref linkend="mysql-connectors"/>.
+ are many others. See
+ <xref linkend="mysql-connectors"/>.
</para>
</listitem>
@@ -1324,14 +1330,14 @@
</indexterm>
<para>
- This section addresses the questions, ``<emphasis>How stable is
- MySQL Server?</emphasis>'' and, ``<emphasis>Can I depend on
- MySQL Server in this project?</emphasis>'' We will try to
- clarify these issues and answer some important questions that
- concern many potential users. The information in this section is
- based on data gathered from the mailing lists, which are very
- active in identifying problems as well as reporting types of
- use.
+ This section addresses the questions, <quote><emphasis>How
+ stable is MySQL Server?</emphasis></quote> and,
+ <quote><emphasis>Can I depend on MySQL Server in this
+ project?</emphasis></quote> We will try to clarify these issues
+ and answer some important questions that concern many potential
+ users. The information in this section is based on data gathered
+ from the mailing lists, which are very active in identifying
+ problems as well as reporting types of use.
</para>
<para>
@@ -1346,14 +1352,14 @@
<para>
Each release of the MySQL Server has been usable. Problems have
- occurred only when users try code from the ``gray zones.''
- Naturally, new users don't know what the gray zones are; this
- section therefore attempts to document those areas that are
- currently known. The descriptions mostly deal with Version 3.23,
- 4.0 and 4.1 of MySQL Server. All known and reported bugs are
- fixed in the latest version, with the exception of those listed
- in the bugs section, which are design-related. See
- <xref linkend="bugs"/>.
+ occurred only when users try code from the <quote>gray
+ zones.</quote> Naturally, new users don't know what the gray
+ zones are; this section therefore attempts to document those
+ areas that are currently known. The descriptions mostly deal
+ with Version 3.23, 4.0 and 4.1 of MySQL Server. All known and
+ reported bugs are fixed in the latest version, with the
+ exception of those listed in the bugs section, which are
+ design-related. See <xref linkend="bugs"/>.
</para>
<para>
@@ -1744,11 +1750,11 @@
using two-digit values (which are ambiguous) rather than
four-digit values. This problem may be compounded by
applications that use values such as <literal>00</literal> or
- <literal>99</literal> as ``missing'' value indicators.
- Unfortunately, these problems may be difficult to fix because
- different applications may be written by different programmers,
- each of whom may use a different set of conventions and
- date-handling functions.
+ <literal>99</literal> as <quote>missing</quote> value
+ indicators. Unfortunately, these problems may be difficult to
+ fix because different applications may be written by different
+ programmers, each of whom may use a different set of conventions
+ and date-handling functions.
</para>
<para>
@@ -2549,13 +2555,13 @@
server is installed (including the platform type and version
number). This is highly relevant information, and in 99 cases
out of 100, the bug report is useless without it. Very often
- we get questions like, ``Why doesn't this work for me?'' Then
- we find that the feature requested wasn't implemented in that
- MySQL version, or that a bug described in a report has been
- fixed in newer MySQL versions. Sometimes the error is
- platform-dependent; in such cases, it is next to impossible
- for us to fix anything without knowing the operating system
- and the version number of the platform.
+ we get questions like, <quote>Why doesn't this work for
+ me?</quote> Then we find that the feature requested wasn't
+ implemented in that MySQL version, or that a bug described in
+ a report has been fixed in newer MySQL versions. Sometimes the
+ error is platform-dependent; in such cases, it is next to
+ impossible for us to fix anything without knowing the
+ operating system and the version number of the platform.
</para>
<para>
@@ -2641,9 +2647,9 @@
The operating system name and version. If you work with
Windows, you can usually get the name and version number
by double-clicking your My Computer icon and pulling down
- the ``Help/About Windows'' menu. For most Unix-like
- operating systems, you can get this information by
- executing the command <literal>uname -a</literal>.
+ the <quote>Help/About Windows</quote> menu. For most
+ Unix-like operating systems, you can get this information
+ by executing the command <literal>uname -a</literal>.
</para>
</listitem>
@@ -3191,11 +3197,12 @@
<para>
The SQL standard has been evolving since 1986 and several versions
- exist. In this manual, ``SQL-92'' refers to the standard released
- in 1992, ``SQL:1999'' refers to the standard released in 1999, and
- ``SQL:2003'' refers to the current version of the standard. We use
- the phrase ``the SQL standard'' to mean the current version of the
- SQL Standard at any time.
+ exist. In this manual, <quote>SQL-92</quote> refers to the
+ standard released in 1992, <quote>SQL:1999</quote> refers to the
+ standard released in 1999, and <quote>SQL:2003</quote> refers to
+ the current version of the standard. We use the phrase <quote>the
+ SQL standard</quote> to mean the current version of the SQL
+ Standard at any time.
</para>
<para>
@@ -4005,10 +4012,11 @@
<para>
MySQL 4.1 supports subqueries and derived tables. A
- ``subquery'' is a <literal>SELECT</literal> statement nested
- within another statement. A ``derived table'' (an unnamed
- view) is a subquery in the <literal>FROM</literal> clause of
- another statement. See <xref linkend="subqueries"/>.
+ <quote>subquery</quote> is a <literal>SELECT</literal>
+ statement nested within another statement. A <quote>derived
+ table</quote> (an unnamed view) is a subquery in the
+ <literal>FROM</literal> clause of another statement. See
+ <xref linkend="subqueries"/>.
</para>
<para>
@@ -4111,11 +4119,11 @@
<para>
The other non-transactional storage engines in MySQL Server
(such as <literal>MyISAM</literal>) follow a different
- paradigm for data integrity called ``atomic operations.'' In
- transactional terms, <literal>MyISAM</literal> tables
- effectively always operate in <literal>AUTOCOMMIT=1</literal>
- mode. Atomic operations often offer comparable integrity with
- higher performance.
+ paradigm for data integrity called <quote>atomic
+ operations.</quote> In transactional terms,
+ <literal>MyISAM</literal> tables effectively always operate in
+ <literal>AUTOCOMMIT=1</literal> mode. Atomic operations often
+ offer comparable integrity with higher performance.
</para>
<para>
@@ -4226,12 +4234,13 @@
</para>
<para>
- ``Atomic,'' in the sense that we mean it, is nothing magical.
- It only means that you can be sure that while each specific
- update is running, no other user can interfere with it, and
- there can never be an automatic rollback (which can happen
- with transactional tables if you are not very careful). MySQL
- Server also guarantees that there are no dirty reads.
+ <quote>Atomic,</quote> in the sense that we mean it, is
+ nothing magical. It only means that you can be sure that while
+ each specific update is running, no other user can interfere
+ with it, and there can never be an automatic rollback (which
+ can happen with transactional tables if you are not very
+ careful). MySQL Server also guarantees that there are no dirty
+ reads.
</para>
<para>
@@ -4327,11 +4336,11 @@
compared to the original row. The test for changed data is
done with the <literal>WHERE</literal> clause in the
<literal>UPDATE</literal> statement. If the record wasn't
- updated, we give the client a message: ``Some of the data
- you have changed has been changed by another user.'' Then
- we show the old row versus the new row in a window so that
- the user can decide which version of the customer record
- to use.
+ updated, we give the client a message: <quote>Some of the
+ data you have changed has been changed by another
+ user.</quote> Then we show the old row versus the new row
+ in a window so that the user can decide which version of
+ the customer record to use.
</para>
<para>
@@ -4687,9 +4696,10 @@
<para>
In designing an implementation of views, our ambitious goal,
as much as is possible within the confines of SQL, has been
- full compliance with ``Codd's Rule #6'' for relational
- database systems: ``All views that are theoretically
- updatable, should in practice also be updatable.''
+ full compliance with <quote>Codd's Rule #6</quote> for
+ relational database systems: <quote>All views that are
+ theoretically updatable, should in practice also be
+ updatable.</quote>
</para>
</section>
@@ -4797,9 +4807,9 @@
</programlisting>
<para>
- You can also edit the command file ``in place'' to change the
- '<literal>--</literal>' comments to '<literal>#</literal>'
- comments:
+ You can also edit the command file <quote>in place</quote> to
+ change the '<literal>--</literal>' comments to
+ '<literal>#</literal>' comments:
</para>
<programlisting>
@@ -4972,11 +4982,11 @@
<para>
The following holds true when you are not using strict mode.
- If you insert an ``incorrect'' value into a column, such as a
- <literal>NULL</literal> into a <literal>NOT NULL</literal>
- column or a too-large numeric value into a numeric column,
- MySQL sets the column to the ``best possible value'' instead
- of producing an error:
+ If you insert an <quote>incorrect</quote> value into a column,
+ such as a <literal>NULL</literal> into a <literal>NOT
+ NULL</literal> column or a too-large numeric value into a
+ numeric column, MySQL sets the column to the <quote>best
+ possible value</quote> instead of producing an error:
</para>
<itemizedlist>
@@ -5031,8 +5041,8 @@
implicit default value for the column data type. In
general, this is <literal>0</literal> for numeric types,
the empty string (<literal>''</literal>) for string types,
- and the ``zero'' value for date and time types. Implicit
- default values are discussed in
+ and the <quote>zero</quote> value for date and time types.
+ Implicit default values are discussed in
<xref linkend="create-table"/>.
</para>
</listitem>
@@ -5056,10 +5066,10 @@
can't just roll back if we encounter a problem after updating
a few rows, because the storage engine may not support
rollback. The option of terminating the statement is not that
- good; in this case, the update would be ``half done,'' which
- is probably the worst possible scenario. In this case, it's
- better to ``do the best you can'' and then continue as if
- nothing happened.
+ good; in this case, the update would be <quote>half
+ done,</quote> which is probably the worst possible scenario.
+ In this case, it's better to <quote>do the best you
+ can</quote> and then continue as if nothing happened.
</para>
<para>
--- 1.17/refman/introduction.xml 2005-07-25 21:15:21 -05:00
+++ 1.18/refman/introduction.xml 2005-07-26 21:20:43 -05:00
@@ -136,9 +136,10 @@
</para>
<para>
- Reports of errors (often called ``bugs''), as well as questions and
- comments, should be sent to <ulink url="http://bugs.mysql.com"/>.
- See <xref linkend="bug-reports"/>.
+ Reports of errors (often called <quote>bugs</quote>), as well as
+ questions and comments, should be sent to
+ <ulink url="http://bugs.mysql.com"/>. See
+ <xref linkend="bug-reports"/>.
</para>
<para>
@@ -232,9 +233,9 @@
<para>
This manual was initially written by David Axmark and Michael
- ``Monty'' Widenius. It is maintained by the MySQL Documentation
- Team, consisting of Paul DuBois, Stefan Hinz, Mike Hillyer, and
- Jon Stephens. For the many other contributors, see
+ <quote>Monty</quote> Widenius. It is maintained by the MySQL
+ Documentation Team, consisting of Paul DuBois, Stefan Hinz, Mike
+ Hillyer, and Jon Stephens. For the many other contributors, see
<xref linkend="credits"/>.
</para>
@@ -284,9 +285,9 @@
<para>
<literal>Text in this style</literal> is used for SQL
statements; database, table, and column names; C and Perl
- code; and environment variables. Example: ``To reload the
+ code; and environment variables. Example: <quote>To reload the
grant tables, use the <literal>FLUSH PRIVILEGES</literal>
- statement.''
+ statement.</quote>
</para>
<!-- @item -->
@@ -306,16 +307,16 @@
<listitem>
<para>
- Filenames and directory names are written like this: ``The
- global <filename>my.cnf</filename> file is located in the
- <filename>/etc</filename> directory.''
+ Filenames and directory names are written like this:
+ <quote>The global <filename>my.cnf</filename> file is located
+ in the <filename>/etc</filename> directory.</quote>
</para>
</listitem>
<listitem>
<para>
- Character sequences are written like this: ``To specify a
- wildcard, use the '<literal>%</literal>' character.''
+ Character sequences are written like this: <quote>To specify a
+ wildcard, use the '<literal>%</literal>' character.</quote>
</para>
</listitem>
@@ -349,8 +350,8 @@
</programlisting>
<para>
- The ``shell'' is your command interpreter. On Unix, this is
- typically a program such as <command>sh</command> or
+ The <quote>shell</quote> is your command interpreter. On Unix,
+ this is typically a program such as <command>sh</command> or
<command>csh</command>. On Windows, the equivalent program is
<command>command.com</command> or <command>cmd.exe</command>,
typically run in a console window.
@@ -486,7 +487,7 @@
<para>
MySQL AB is the company of the MySQL founders and main developers.
MySQL AB was originally established in Sweden by David Axmark,
- Allan Larsson, and Michael ``Monty'' Widenius.
+ Allan Larsson, and Michael <quote>Monty</quote> Widenius.
</para>
<para>
@@ -598,10 +599,11 @@
</para>
<para>
- By the way, the ``AB'' part of the company name is the acronym for
- the Swedish ``aktiebolag,'' or ``stock company.'' It translates to
- ``MySQL, Inc.'' In fact, MySQL, Inc. and MySQL GmbH are examples
- of MySQL AB subsidiaries. They are located in the US and Germany,
+ By the way, the <quote>AB</quote> part of the company name is the
+ acronym for the Swedish <quote>aktiebolag,</quote> or <quote>stock
+ company.</quote> It translates to <quote>MySQL, Inc.</quote> In
+ fact, MySQL, Inc. and MySQL GmbH are examples of MySQL AB
+ subsidiaries. They are located in the US and Germany,
respectively.
</para>
@@ -667,16 +669,17 @@
A relational database stores data in separate tables rather
than putting all the data in one big storeroom. This adds
- speed and flexibility. The SQL part of ``MySQL'' stands for
- ``Structured Query Language.'' SQL is the most common
- standardized language used to access databases and is defined
- by the ANSI/ISO SQL Standard. The SQL standard has been
- evolving since 1986 and several versions exist. In this
- manual, ``SQL-92'' refers to the standard released in 1992,
- ``SQL:1999'' refers to the standard released in 1999, and
- ``SQL:2003'' refers to the current version of the standard. We
- use the phrase ``the SQL standard'' to mean the current
- version of the SQL Standard at any time.
+ speed and flexibility. The SQL part of <quote>MySQL</quote>
+ stands for <quote>Structured Query Language.</quote> SQL is
+ the most common standardized language used to access databases
+ and is defined by the ANSI/ISO SQL Standard. The SQL standard
+ has been evolving since 1986 and several versions exist. In
+ this manual, <quote>SQL-92</quote> refers to the standard
+ released in 1992, <quote>SQL:1999</quote> refers to the
+ standard released in 1999, and <quote>SQL:2003</quote> refers
+ to the current version of the standard. We use the phrase
+ <quote>the SQL standard</quote> to mean the current version of
+ the SQL Standard at any time.
</para>
</listitem>
@@ -793,9 +796,10 @@
</indexterm>
<para>
- The official way to pronounce ``MySQL'' is ``My Ess Que Ell'' (not
- ``my sequel''), but we don't mind if you pronounce it as ``my
- sequel'' or in some other localized way.
+ The official way to pronounce <quote>MySQL</quote> is <quote>My
+ Ess Que Ell</quote> (not <quote>my sequel</quote>), but we don't
+ mind if you pronounce it as <quote>my sequel</quote> or in some
+ other localized way.
</para>
<section id="history">
@@ -842,20 +846,21 @@
<para>
The derivation of the name MySQL is not clear. Our base
directory and a large number of our libraries and tools have had
- the prefix ``my'' for well over 10 years. However, co-founder
- Monty Widenius's daughter is also named My. Which of the two
- gave its name to MySQL is still a mystery, even for us.
+ the prefix <quote>my</quote> for well over 10 years. However,
+ co-founder Monty Widenius's daughter is also named My. Which of
+ the two gave its name to MySQL is still a mystery, even for us.
</para>
<para>
- The name of the MySQL Dolphin (our logo) is ``Sakila,'' which
- was chosen by the founders of MySQL AB from a huge list of names
- suggested by users in our ``Name the Dolphin'' contest. The
- winning name was submitted by Ambrose Twebaze, an Open Source
- software developer from Swaziland, Africa. According to Ambrose,
- the feminine name Sakila has its roots in SiSwati, the local
- language of Swaziland. Sakila is also the name of a town in
- Arusha, Tanzania, near Ambrose's country of origin, Uganda.
+ The name of the MySQL Dolphin (our logo) is
+ <quote>Sakila,</quote> which was chosen by the founders of MySQL
+ AB from a huge list of names suggested by users in our
+ <quote>Name the Dolphin</quote> contest. The winning name was
+ submitted by Ambrose Twebaze, an Open Source software developer
+ from Swaziland, Africa. According to Ambrose, the feminine name
+ Sakila has its roots in SiSwati, the local language of
+ Swaziland. Sakila is also the name of a town in Arusha,
+ Tanzania, near Ambrose's country of origin, Uganda.
</para>
</section>
@@ -1215,7 +1220,8 @@
can use MS Access to connect to your MySQL server.
Clients can be run on Windows or Unix. MyODBC source
is available. All ODBC 2.5 functions are supported, as
- are many others. See <xref linkend="mysql-connectors"/>.
+ are many others. See
+ <xref linkend="mysql-connectors"/>.
</para>
</listitem>
@@ -1327,14 +1333,14 @@
</indexterm>
<para>
- This section addresses the questions, ``<emphasis>How stable is
- MySQL Server?</emphasis>'' and, ``<emphasis>Can I depend on
- MySQL Server in this project?</emphasis>'' We will try to
- clarify these issues and answer some important questions that
- concern many potential users. The information in this section is
- based on data gathered from the mailing lists, which are very
- active in identifying problems as well as reporting types of
- use.
+ This section addresses the questions, <quote><emphasis>How
+ stable is MySQL Server?</emphasis></quote> and,
+ <quote><emphasis>Can I depend on MySQL Server in this
+ project?</emphasis></quote> We will try to clarify these issues
+ and answer some important questions that concern many potential
+ users. The information in this section is based on data gathered
+ from the mailing lists, which are very active in identifying
+ problems as well as reporting types of use.
</para>
<para>
@@ -1351,14 +1357,14 @@
<para>
Each release of the MySQL Server has been usable. Problems have
- occurred only when users try code from the ``gray zones.''
- Naturally, new users don't know what the gray zones are; this
- section therefore attempts to document those areas that are
- currently known. The descriptions mostly deal with Version 3.23,
- 4.0 and 4.1 of MySQL Server. All known and reported bugs are
- fixed in the latest version, with the exception of those listed
- in the bugs section, which are design-related. See
- <xref linkend="bugs"/>.
+ occurred only when users try code from the <quote>gray
+ zones.</quote> Naturally, new users don't know what the gray
+ zones are; this section therefore attempts to document those
+ areas that are currently known. The descriptions mostly deal
+ with Version 3.23, 4.0 and 4.1 of MySQL Server. All known and
+ reported bugs are fixed in the latest version, with the
+ exception of those listed in the bugs section, which are
+ design-related. See <xref linkend="bugs"/>.
</para>
<para>
@@ -1762,11 +1768,11 @@
using two-digit values (which are ambiguous) rather than
four-digit values. This problem may be compounded by
applications that use values such as <literal>00</literal> or
- <literal>99</literal> as ``missing'' value indicators.
- Unfortunately, these problems may be difficult to fix because
- different applications may be written by different programmers,
- each of whom may use a different set of conventions and
- date-handling functions.
+ <literal>99</literal> as <quote>missing</quote> value
+ indicators. Unfortunately, these problems may be difficult to
+ fix because different applications may be written by different
+ programmers, each of whom may use a different set of conventions
+ and date-handling functions.
</para>
<para>
@@ -2220,11 +2226,12 @@
<listitem>
<para>
- A ``subquery'' is a <literal>SELECT</literal>
- statement nested within another statement. A
- ``derived table'' (an unnamed view) is a subquery in
- the <literal>FROM</literal> clause of another
- statement. See <xref linkend="subqueries"/>.
+ A <quote>subquery</quote> is a
+ <literal>SELECT</literal> statement nested within
+ another statement. A <quote>derived table</quote>
+ (an unnamed view) is a subquery in the
+ <literal>FROM</literal> clause of another statement.
+ See <xref linkend="subqueries"/>.
</para>
</listitem>
@@ -3102,13 +3109,13 @@
server is installed (including the platform type and version
number). This is highly relevant information, and in 99 cases
out of 100, the bug report is useless without it. Very often
- we get questions like, ``Why doesn't this work for me?'' Then
- we find that the feature requested wasn't implemented in that
- MySQL version, or that a bug described in a report has been
- fixed in newer MySQL versions. Sometimes the error is
- platform-dependent; in such cases, it is next to impossible
- for us to fix anything without knowing the operating system
- and the version number of the platform.
+ we get questions like, <quote>Why doesn't this work for
+ me?</quote> Then we find that the feature requested wasn't
+ implemented in that MySQL version, or that a bug described in
+ a report has been fixed in newer MySQL versions. Sometimes the
+ error is platform-dependent; in such cases, it is next to
+ impossible for us to fix anything without knowing the
+ operating system and the version number of the platform.
</para>
<para>
@@ -3194,9 +3201,9 @@
The operating system name and version. If you work with
Windows, you can usually get the name and version number
by double-clicking your My Computer icon and pulling down
- the ``Help/About Windows'' menu. For most Unix-like
- operating systems, you can get this information by
- executing the command <literal>uname -a</literal>.
+ the <quote>Help/About Windows</quote> menu. For most
+ Unix-like operating systems, you can get this information
+ by executing the command <literal>uname -a</literal>.
</para>
</listitem>
@@ -3744,11 +3751,12 @@
<para>
The SQL standard has been evolving since 1986 and several versions
- exist. In this manual, ``SQL-92'' refers to the standard released
- in 1992, ``SQL:1999'' refers to the standard released in 1999, and
- ``SQL:2003'' refers to the current version of the standard. We use
- the phrase ``the SQL standard'' to mean the current version of the
- SQL Standard at any time.
+ exist. In this manual, <quote>SQL-92</quote> refers to the
+ standard released in 1992, <quote>SQL:1999</quote> refers to the
+ standard released in 1999, and <quote>SQL:2003</quote> refers to
+ the current version of the standard. We use the phrase <quote>the
+ SQL standard</quote> to mean the current version of the SQL
+ Standard at any time.
</para>
<para>
@@ -4554,10 +4562,11 @@
<para>
MySQL 4.1 supports subqueries and derived tables. A
- ``subquery'' is a <literal>SELECT</literal> statement nested
- within another statement. A ``derived table'' (an unnamed
- view) is a subquery in the <literal>FROM</literal> clause of
- another statement. See <xref linkend="subqueries"/>.
+ <quote>subquery</quote> is a <literal>SELECT</literal>
+ statement nested within another statement. A <quote>derived
+ table</quote> (an unnamed view) is a subquery in the
+ <literal>FROM</literal> clause of another statement. See
+ <xref linkend="subqueries"/>.
</para>
<para>
@@ -4660,11 +4669,11 @@
<para>
The other non-transactional storage engines in MySQL Server
(such as <literal>MyISAM</literal>) follow a different
- paradigm for data integrity called ``atomic operations.'' In
- transactional terms, <literal>MyISAM</literal> tables
- effectively always operate in <literal>AUTOCOMMIT=1</literal>
- mode. Atomic operations often offer comparable integrity with
- higher performance.
+ paradigm for data integrity called <quote>atomic
+ operations.</quote> In transactional terms,
+ <literal>MyISAM</literal> tables effectively always operate in
+ <literal>AUTOCOMMIT=1</literal> mode. Atomic operations often
+ offer comparable integrity with higher performance.
</para>
<para>
@@ -4775,12 +4784,13 @@
</para>
<para>
- ``Atomic,'' in the sense that we mean it, is nothing magical.
- It only means that you can be sure that while each specific
- update is running, no other user can interfere with it, and
- there can never be an automatic rollback (which can happen
- with transactional tables if you are not very careful). MySQL
- Server also guarantees that there are no dirty reads.
+ <quote>Atomic,</quote> in the sense that we mean it, is
+ nothing magical. It only means that you can be sure that while
+ each specific update is running, no other user can interfere
+ with it, and there can never be an automatic rollback (which
+ can happen with transactional tables if you are not very
+ careful). MySQL Server also guarantees that there are no dirty
+ reads.
</para>
<para>
@@ -4876,11 +4886,11 @@
compared to the original row. The test for changed data is
done with the <literal>WHERE</literal> clause in the
<literal>UPDATE</literal> statement. If the record wasn't
- updated, we give the client a message: ``Some of the data
- you have changed has been changed by another user.'' Then
- we show the old row versus the new row in a window so that
- the user can decide which version of the customer record
- to use.
+ updated, we give the client a message: <quote>Some of the
+ data you have changed has been changed by another
+ user.</quote> Then we show the old row versus the new row
+ in a window so that the user can decide which version of
+ the customer record to use.
</para>
<para>
@@ -5236,9 +5246,10 @@
<para>
In designing an implementation of views, our ambitious goal,
as much as is possible within the confines of SQL, has been
- full compliance with ``Codd's Rule #6'' for relational
- database systems: ``All views that are theoretically
- updatable, should in practice also be updatable.''
+ full compliance with <quote>Codd's Rule #6</quote> for
+ relational database systems: <quote>All views that are
+ theoretically updatable, should in practice also be
+ updatable.</quote>
</para>
</section>
@@ -5346,9 +5357,9 @@
</programlisting>
<para>
- You can also edit the command file ``in place'' to change the
- '<literal>--</literal>' comments to '<literal>#</literal>'
- comments:
+ You can also edit the command file <quote>in place</quote> to
+ change the '<literal>--</literal>' comments to
+ '<literal>#</literal>' comments:
</para>
<programlisting>
@@ -5517,11 +5528,11 @@
<para>
The following holds true when you are not using strict mode.
- If you insert an ``incorrect'' value into a column, such as a
- <literal>NULL</literal> into a <literal>NOT NULL</literal>
- column or a too-large numeric value into a numeric column,
- MySQL sets the column to the ``best possible value'' instead
- of producing an error:
+ If you insert an <quote>incorrect</quote> value into a column,
+ such as a <literal>NULL</literal> into a <literal>NOT
+ NULL</literal> column or a too-large numeric value into a
+ numeric column, MySQL sets the column to the <quote>best
+ possible value</quote> instead of producing an error:
</para>
<itemizedlist>
@@ -5576,8 +5587,8 @@
implicit default value for the column data type. In
general, this is <literal>0</literal> for numeric types,
the empty string (<literal>''</literal>) for string types,
- and the ``zero'' value for date and time types. Implicit
- default values are discussed in
+ and the <quote>zero</quote> value for date and time types.
+ Implicit default values are discussed in
<xref linkend="create-table"/>.
</para>
</listitem>
@@ -5601,10 +5612,10 @@
can't just roll back if we encounter a problem after updating
a few rows, because the storage engine may not support
rollback. The option of terminating the statement is not that
- good; in this case, the update would be ``half done,'' which
- is probably the worst possible scenario. In this case, it's
- better to ``do the best you can'' and then continue as if
- nothing happened.
+ good; in this case, the update would be <quote>half
+ done,</quote> which is probably the worst possible scenario.
+ In this case, it's better to <quote>do the best you
+ can</quote> and then continue as if nothing happened.
</para>
<para>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.3137) | paul | 27 Jul |
