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.2992 05/07/11 15:36:48 paul@stripped +3 -0
Format.
refman/introduction.xml
1.11 05/07/11 15:36:47 paul@stripped +340 -346
Format.
refman-5.0/introduction.xml
1.12 05/07/11 15:36:47 paul@stripped +415 -424
Format.
refman-4.1/introduction.xml
1.13 05/07/11 15:36:47 paul@stripped +385 -388
Format.
# 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: kite-hub.kitebird.com
# Root: /src/extern/MySQL/bk/mysqldoc
--- 1.12/refman-4.1/introduction.xml 2005-07-11 15:35:08 -05:00
+++ 1.13/refman-4.1/introduction.xml 2005-07-11 15:36:47 -05:00
@@ -159,16 +159,20 @@
<secondary>online location</secondary>
</indexterm>
- <!-- NOTE: Next para also appears in preface.xml -->
-
+<!-- NOTE: Next para also appears in preface.xml -->
+
<para>
- This is the Reference Manual for all releases of the MySQL Database
- System through Version ¤t-version;. It is applicable for older
- versions of the MySQL software (such as 3.23 or 4.0-production)
- because functional changes are indicated with reference to a version
- number. <!-- Update following as appropriate. --> For later MySQL
- releases, see the appropriately-numbered edition of this manual.
- </para>
+ This is the Reference Manual for all releases of the MySQL Database
+ System through Version ¤t-version;. It is applicable for older
+ versions of the MySQL software (such as 3.23 or 4.0-production)
+ because functional changes are indicated with reference to a version
+ number.
+
+<!-- Update following as appropriate. -->
+
+ For later MySQL releases, see the appropriately-numbered edition of
+ this manual.
+ </para>
<para>
Because this manual serves as a reference, it does not provide
@@ -195,15 +199,17 @@
<primary>Texinfo</primary>
</indexterm>
- <!-- Next paragraph needs to be updated. -->
-
+<!-- Next paragraph needs to be updated. -->
+
<para>
- The primary document is a set of
- <ulink url="http://docbook.org/">DocBook</ulink> XML files.
- The HTML version and other formats are produced automatically using,
- among other tools, the
- <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/reference.html">DocBook XSL stylesheets</ulink>.
- <!-- [SH] We might want to add details about creating CHM, PDF, INFO, ... -->
+ The primary document is a set of
+ <ulink url="http://docbook.org/">DocBook</ulink> XML files. The HTML
+ version and other formats are produced automatically using, among
+ other tools, the
+ <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/reference.html">DocBook
+ XSL stylesheets</ulink>.
+
+<!-- [SH] We might want to add details about creating CHM, PDF, INFO, ... -->
</para>
<para>
@@ -211,23 +217,23 @@
this manual, please send them to the documentation team at
<email>docs@stripped</email>.
</para>
-
- <!-- Next paragraph needs to be updated. -->
-
+
+<!-- Next paragraph needs to be updated. -->
+
<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
+ consisting of Paul DuBois, Stefan Hinz, Mike Hillyer, and Jon
+ Stephens. For the many other contributors, see
<xref linkend="credits"/>.
</para>
<para>
- The copyright to this manual is owned by the Swedish company
- MySQL AB. MySQL and the MySQL logo are (registered) trademarks of
- MySQL AB. Other trademarks and registered trademarks referred to in
- this manual are the property of their respective owners, and are used
- for identification purposes only.
+ The copyright to this manual is owned by the Swedish company MySQL
+ AB. MySQL and the MySQL logo are (registered) trademarks of MySQL AB.
+ Other trademarks and registered trademarks referred to in this manual
+ are the property of their respective owners, and are used for
+ identification purposes only.
</para>
</section>
@@ -779,10 +785,10 @@
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.
+ 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>
@@ -1272,9 +1278,9 @@
<para>
MySQL 3.22 had a 4GB (4 gigabyte) limit on table size. With the
<literal>MyISAM</literal> storage engine in MySQL 3.23, the maximum
- table size was increased to 65536 terabytes (256 ^ 7 - 1 bytes). With
- this larger allowed table size, the maximum effective table size for
- MySQL databases is usually determined by operating system
+ table size was increased to 65536 terabytes (256 ^ 7 - 1 bytes).
+ With this larger allowed table size, the maximum effective table
+ size for MySQL databases is usually determined by operating system
constraints on file sizes, not by MySQL internal limits.
</para>
@@ -1880,38 +1886,37 @@
forgotten requests from our loyal community of existing users.
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- Most <command>mysqld</command> parameters (startup options) can
- be set without taking down the server. This is a convenient
- feature for database administrators (DBAs). See
- <xref linkend="set-option"/>.
- </para></listitem>
+ <listitem><para>
+ Most <command>mysqld</command> parameters (startup options) can
+ be set without taking down the server. This is a convenient
+ feature for database administrators (DBAs). See
+ <xref linkend="set-option"/>.
+ </para></listitem>
- <listitem><para>
- Multiple-table <literal>DELETE</literal> and
- <literal>UPDATE</literal> statements have been added.
- </para></listitem>
+ <listitem><para>
+ Multiple-table <literal>DELETE</literal> and
+ <literal>UPDATE</literal> statements have been added.
+ </para></listitem>
- <listitem><para>
- On Windows, symbolic link handling at the database level is
- enabled by default. On Unix, the <literal>MyISAM</literal>
- storage engine supports symbolic linking at the table level (and
- not just the database level as before).
- </para></listitem>
+ <listitem><para>
+ On Windows, symbolic link handling at the database level is
+ enabled by default. On Unix, the <literal>MyISAM</literal>
+ storage engine supports symbolic linking at the table level (and
+ not just the database level as before).
+ </para></listitem>
- <listitem><para>
- <literal>SQL_CALC_FOUND_ROWS</literal> and
- <literal>FOUND_ROWS()</literal> are new functions that make it
- possible to find out the number of rows a
- <literal>SELECT</literal> query that includes a
- <literal>LIMIT</literal> clause would have returned without that
- clause.
- </para></listitem>
+ <listitem><para>
+ <literal>SQL_CALC_FOUND_ROWS</literal> and
+ <literal>FOUND_ROWS()</literal> are new functions that make it
+ possible to find out the number of rows a
+ <literal>SELECT</literal> query that includes a
+ <literal>LIMIT</literal> clause would have returned without that
+ clause.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
</itemizedlist>
@@ -1988,10 +1993,11 @@
<para>
MySQL Server 4.0 laid the foundation for new features implemented in
- MySQL 4.1, such as subqueries and Unicode support. These features come
- at the top of the wish list of many of our customers. Well-known for
- its stability, speed, and ease of use, MySQL Server is able to
- fulfill the requirement checklists of very demanding buyers.
+ MySQL 4.1, such as subqueries and Unicode support. These features
+ come at the top of the wish list of many of our customers.
+ Well-known for its stability, speed, and ease of use, MySQL Server
+ is able to fulfill the requirement checklists of very demanding
+ buyers.
</para>
<para>
@@ -2190,8 +2196,8 @@
</section>
</section>
-
- <!--
+
+<!--
TODO: Update the intro to provide an overview of all information
resources, including the user forums.
-->
@@ -2212,11 +2218,11 @@
<indexterm type="concept">
<primary>errors</primary>
<secondary>reporting</secondary>
- </indexterm>
-
- <indexterm type="concept">
+ </indexterm>
+
+ <indexterm type="concept">
<primary>MySQL mailing lists</primary>
- </indexterm>
+ </indexterm>
<para>
This section introduces the MySQL mailing lists and provides
@@ -2426,7 +2432,7 @@
<para>
If you're unable to get an answer to your questions from a MySQL
- mailing list or forum, one option is to purchase support from MySQL
+ mailing list or forum, one option is to purchase support from MySQL
AB. This puts you in direct contact with MySQL developers.
</para>
@@ -2992,9 +2998,8 @@
<para>
If you are running Windows, please verify the value of
- <literal>lower_case_table_names</literal> using the
- <literal>SHOW VARIABLES LIKE 'lower_case_table_names'</literal>
- command.
+ <literal>lower_case_table_names</literal> using the <literal>SHOW
+ VARIABLES LIKE 'lower_case_table_names'</literal> command.
</para></listitem>
<listitem><para>
@@ -3155,11 +3160,11 @@
</itemizedlist>
- <!--
+<!--
TODO: Update following paragraph, as the win32 version is no
longer free.
-->
-
+
<para>
If you are looking for IRC client software to connect to an IRC
network, take a look at <literal>xChat</literal>
@@ -3198,7 +3203,7 @@
<listitem><para>
MySQL Usage
</para></listitem>
-
+
<listitem><para>
MySQL Connectors
</para></listitem>
@@ -3206,23 +3211,23 @@
<listitem><para>
Programming Languages
</para></listitem>
-
+
<listitem><para>
- Tools
+ Tools
</para></listitem>
-
+
<listitem><para>
- 3rd-Party Applications
+ 3rd-Party Applications
</para></listitem>
<listitem><para>
Storage Engines
</para></listitem>
-
+
<listitem><para>
MySQL Technology
</para></listitem>
-
+
<listitem><para>
SQL Standards
</para></listitem>
@@ -3283,10 +3288,10 @@
</para>
<para>
- Our goal is to not restrict MySQL Server's usability without a very
- good reason for doing so. Even if we don't have the resources to
- perform development for every possible use, we are always willing to
- help and offer suggestions to people who are trying to use MySQL
+ Our goal is to not restrict MySQL Server's usability without a very
+ good reason for doing so. Even if we don't have the resources to
+ perform development for every possible use, we are always willing to
+ help and offer suggestions to people who are trying to use MySQL
Server in new areas.
</para>
@@ -3508,45 +3513,45 @@
database directory. This has a few implications:
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><indexterm type="concept">
- <primary>database names</primary>
- <secondary>case-sensitivity</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>case-sensitivity</primary>
- <secondary>of database names</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>table names</primary>
- <secondary>case-sensitivity</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>case-sensitivity</primary>
- <secondary>of table names</secondary>
- </indexterm>
-
- <para>
- Database names and table names are case sensitive in MySQL Server
- on operating systems that have case-sensitive filenames (such as
- most Unix systems). See <xref linkend="name-case-sensitivity"/>.
- </para></listitem>
+ <listitem><indexterm type="concept">
+ <primary>database names</primary>
+ <secondary>case-sensitivity</secondary>
+ </indexterm>
- <listitem><para>
- You can use standard system commands to back up, rename, move,
- delete, and copy tables that are managed by the
- <literal>MyISAM</literal> or <literal>ISAM</literal> storage
- engines. For example, to rename a <literal>MyISAM</literal>
- table, rename the <filename>.MYD</filename>,
- <filename>.MYI</filename>, and <filename>.frm</filename> files to
- which the table corresponds.
- </para></listitem>
+ <indexterm type="concept">
+ <primary>case-sensitivity</primary>
+ <secondary>of database names</secondary>
+ </indexterm>
- </itemizedlist>
+ <indexterm type="concept">
+ <primary>table names</primary>
+ <secondary>case-sensitivity</secondary>
+ </indexterm>
+
+ <indexterm type="concept">
+ <primary>case-sensitivity</primary>
+ <secondary>of table names</secondary>
+ </indexterm>
+
+ <para>
+ Database names and table names are case sensitive in MySQL Server
+ on operating systems that have case-sensitive filenames (such as
+ most Unix systems). See <xref linkend="name-case-sensitivity"/>.
+ </para></listitem>
+
+ <listitem><para>
+ You can use standard system commands to back up, rename, move,
+ delete, and copy tables that are managed by the
+ <literal>MyISAM</literal> or <literal>ISAM</literal> storage
+ engines. For example, to rename a <literal>MyISAM</literal> table,
+ rename the <filename>.MYD</filename>, <filename>.MYI</filename>,
+ and <filename>.frm</filename> files to which the table
+ corresponds.
+ </para></listitem>
+
+ </itemizedlist>
<para>
Database, table, index, column, or alias names may begin with a
@@ -3557,334 +3562,326 @@
General language syntax
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- Strings may be enclosed by either '<literal>"</literal>' or
- '<literal>'</literal>', not just by '<literal>'</literal>'.
- </para></listitem>
+ <listitem><para>
+ Strings may be enclosed by either '<literal>"</literal>' or
+ '<literal>'</literal>', not just by '<literal>'</literal>'.
+ </para></listitem>
- <listitem><para>
- Use of '<literal>\</literal>' as an escape character in strings.
- </para></listitem>
+ <listitem><para>
+ Use of '<literal>\</literal>' as an escape character in strings.
+ </para></listitem>
- <listitem><para>
- In SQL statements, you can access tables from different databases
- with the <replaceable>db_name.tbl_name</replaceable> syntax. Some
- SQL servers provide the same functionality but call this
- <literal>User space</literal>. MySQL Server doesn't support
- tablespaces such as used in statements like this: <literal>CREATE
- TABLE ralph.my_table...IN my_tablespace</literal>.
- </para></listitem>
+ <listitem><para>
+ In SQL statements, you can access tables from different databases
+ with the <replaceable>db_name.tbl_name</replaceable> syntax. Some
+ SQL servers provide the same functionality but call this
+ <literal>User space</literal>. MySQL Server doesn't support
+ tablespaces such as used in statements like this: <literal>CREATE
+ TABLE ralph.my_table...IN my_tablespace</literal>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
SQL statement syntax
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- The <literal>ANALYZE TABLE</literal>, <literal>CHECK
- TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and
- <literal>REPAIR TABLE</literal> statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>ANALYZE TABLE</literal>, <literal>CHECK
+ TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and
+ <literal>REPAIR TABLE</literal> statements.
+ </para></listitem>
- <listitem><para>
- The <literal>CREATE DATABASE</literal> and <literal>DROP
- DATABASE</literal> statements. See
- <xref linkend="create-database"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>CREATE DATABASE</literal> and <literal>DROP
+ DATABASE</literal> statements. See
+ <xref linkend="create-database"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>DO</literal> statement.
- </para></listitem>
+ <listitem><para>
+ The <literal>DO</literal> statement.
+ </para></listitem>
- <listitem><para>
- <literal>EXPLAIN SELECT</literal> to get a description of how
- tables are joined.
- </para></listitem>
+ <listitem><para>
+ <literal>EXPLAIN SELECT</literal> to get a description of how
+ tables are joined.
+ </para></listitem>
- <listitem><para>
- The <literal>FLUSH</literal> and <literal>RESET</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>FLUSH</literal> and <literal>RESET</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- The <literal>SET</literal> statement. See
- <xref linkend="set-option"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>SET</literal> statement. See
+ <xref linkend="set-option"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>SHOW</literal> statement. See
- <xref linkend="show"/>.
- </para>
+ <listitem><para>
+ The <literal>SHOW</literal> statement. See <xref linkend="show"/>.
+ </para>
- <indexterm type="concept">
- <primary>Oracle compatibility</primary>
- </indexterm>
+ <indexterm type="concept">
+ <primary>Oracle compatibility</primary>
+ </indexterm>
- <indexterm type="concept">
- <primary>compatibility</primary>
- <secondary>with Oracle</secondary>
- </indexterm></listitem>
+ <indexterm type="concept">
+ <primary>compatibility</primary>
+ <secondary>with Oracle</secondary>
+ </indexterm></listitem>
- <listitem><para>
- Use of <literal>LOAD DATA INFILE</literal>. In many cases, this
- syntax is compatible with Oracle's <literal>LOAD DATA
- INFILE</literal>. See <xref linkend="load-data"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>LOAD DATA INFILE</literal>. In many cases, this
+ syntax is compatible with Oracle's <literal>LOAD DATA
+ INFILE</literal>. See <xref linkend="load-data"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>RENAME TABLE</literal>. See
- <xref linkend="rename-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>RENAME TABLE</literal>. See
+ <xref linkend="rename-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>REPLACE</literal> instead of
- <literal>DELETE</literal> + <literal>INSERT</literal>. See
- <xref linkend="replace"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>REPLACE</literal> instead of
+ <literal>DELETE</literal> + <literal>INSERT</literal>. See
+ <xref linkend="replace"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>CHANGE col_name</literal>, <literal>DROP
- col_name</literal>, or <literal>DROP INDEX</literal>,
- <literal>IGNORE</literal> or <literal>RENAME</literal> in an
- <literal>ALTER TABLE</literal> statement. Use of multiple
- <literal>ADD</literal>, <literal>ALTER</literal>,
- <literal>DROP</literal>, or <literal>CHANGE</literal> clauses in
- an <literal>ALTER TABLE</literal> statement. See
- <xref linkend="alter-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>CHANGE col_name</literal>, <literal>DROP
+ col_name</literal>, or <literal>DROP INDEX</literal>,
+ <literal>IGNORE</literal> or <literal>RENAME</literal> in an
+ <literal>ALTER TABLE</literal> statement. Use of multiple
+ <literal>ADD</literal>, <literal>ALTER</literal>,
+ <literal>DROP</literal>, or <literal>CHANGE</literal> clauses in
+ an <literal>ALTER TABLE</literal> statement. See
+ <xref linkend="alter-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of index names, indexes on a prefix of a field, and use of
- <literal>INDEX</literal> or <literal>KEY</literal> in a
- <literal>CREATE TABLE</literal> statement. See
- <xref linkend="create-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of index names, indexes on a prefix of a field, and use of
+ <literal>INDEX</literal> or <literal>KEY</literal> in a
+ <literal>CREATE TABLE</literal> statement. See
+ <xref linkend="create-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>TEMPORARY</literal> or <literal>IF NOT
- EXISTS</literal> with <literal>CREATE TABLE</literal>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>TEMPORARY</literal> or <literal>IF NOT
+ EXISTS</literal> with <literal>CREATE TABLE</literal>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>IF EXISTS</literal> with <literal>DROP
- TABLE</literal>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>IF EXISTS</literal> with <literal>DROP
+ TABLE</literal>.
+ </para></listitem>
- <listitem><para>
- You can drop multiple tables with a single <literal>DROP
- TABLE</literal> statement.
- </para></listitem>
+ <listitem><para>
+ You can drop multiple tables with a single <literal>DROP
+ TABLE</literal> statement.
+ </para></listitem>
- <listitem><para>
- The <literal>ORDER BY</literal> and <literal>LIMIT</literal>
- clauses of the <literal>UPDATE</literal> and
- <literal>DELETE</literal> statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>ORDER BY</literal> and <literal>LIMIT</literal>
+ clauses of the <literal>UPDATE</literal> and
+ <literal>DELETE</literal> statements.
+ </para></listitem>
- <listitem><para>
- <literal>INSERT INTO ... SET col_name = ...</literal> syntax.
- </para></listitem>
+ <listitem><para>
+ <literal>INSERT INTO ... SET col_name = ...</literal> syntax.
+ </para></listitem>
- <listitem><para>
- The <literal>DELAYED</literal> clause of the
- <literal>INSERT</literal> and <literal>REPLACE</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>DELAYED</literal> clause of the
+ <literal>INSERT</literal> and <literal>REPLACE</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- The <literal>LOW_PRIORITY</literal> clause of the
- <literal>INSERT</literal>, <literal>REPLACE</literal>,
- <literal>DELETE</literal>, and <literal>UPDATE</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>LOW_PRIORITY</literal> clause of the
+ <literal>INSERT</literal>, <literal>REPLACE</literal>,
+ <literal>DELETE</literal>, and <literal>UPDATE</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- Use of <literal>INTO OUTFILE</literal> and
- <literal>STRAIGHT_JOIN</literal> in a <literal>SELECT</literal>
- statement. See <xref linkend="select"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>INTO OUTFILE</literal> and
+ <literal>STRAIGHT_JOIN</literal> in a <literal>SELECT</literal>
+ statement. See <xref linkend="select"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>SQL_SMALL_RESULT</literal> option in a
- <literal>SELECT</literal> statement.
- </para></listitem>
+ <listitem><para>
+ The <literal>SQL_SMALL_RESULT</literal> option in a
+ <literal>SELECT</literal> statement.
+ </para></listitem>
- <listitem><para>
- You don't need to name all selected columns in the <literal>GROUP
- BY</literal> part. This gives better performance for some very
- specific, but quite normal queries. See
- <xref linkend="group-by-functions-and-modifiers"/>.
- </para></listitem>
+ <listitem><para>
+ You don't need to name all selected columns in the <literal>GROUP
+ BY</literal> part. This gives better performance for some very
+ specific, but quite normal queries. See
+ <xref linkend="group-by-functions-and-modifiers"/>.
+ </para></listitem>
- <listitem><para>
- You can specify <literal>ASC</literal> and
- <literal>DESC</literal> with <literal>GROUP BY</literal>.
- </para></listitem>
+ <listitem><para>
+ You can specify <literal>ASC</literal> and <literal>DESC</literal>
+ with <literal>GROUP BY</literal>.
+ </para></listitem>
- <listitem><para>
- The ability to set variables in a statement with the
- <literal>:=</literal> assignment operator:
+ <listitem><para>
+ The ability to set variables in a statement with the
+ <literal>:=</literal> assignment operator:
<programlisting>
mysql> SELECT @a:=SUM(total),@b=COUNT(*),@a/@b AS avg
-> FROM test_table;
mysql> SELECT @t1:=(@t2:=1)+@t3:=4,@t1,@t2,@t3;
</programlisting>
- </para></listitem>
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
Column types
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- The column types <literal>MEDIUMINT</literal>,
- <literal>SET</literal>, <literal>ENUM</literal>, and the
- different <literal>BLOB</literal> and <literal>TEXT</literal>
- types.
- </para></listitem>
+ <listitem><para>
+ The column types <literal>MEDIUMINT</literal>,
+ <literal>SET</literal>, <literal>ENUM</literal>, and the different
+ <literal>BLOB</literal> and <literal>TEXT</literal> types.
+ </para></listitem>
- <listitem><para>
- The column attributes <literal>AUTO_INCREMENT</literal>,
- <literal>BINARY</literal>, <literal>NULL</literal>,
- <literal>UNSIGNED</literal>, and <literal>ZEROFILL</literal>.
- </para></listitem>
+ <listitem><para>
+ The column attributes <literal>AUTO_INCREMENT</literal>,
+ <literal>BINARY</literal>, <literal>NULL</literal>,
+ <literal>UNSIGNED</literal>, and <literal>ZEROFILL</literal>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
Functions and operators
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- To make it easier for users who come from other SQL environments,
- MySQL Server supports aliases for many functions. For example,
- all string functions support both standard SQL syntax and ODBC
- syntax.
- </para></listitem>
+ <listitem><para>
+ To make it easier for users who come from other SQL environments,
+ MySQL Server supports aliases for many functions. For example, all
+ string functions support both standard SQL syntax and ODBC syntax.
+ </para></listitem>
- <listitem><para>
- MySQL Server understands the <literal>||</literal> and
- <literal>&&</literal> operators to mean logical OR and
- AND, as in the C programming language. In MySQL Server,
- <literal>||</literal> and <literal>OR</literal> are synonyms, as
- are <literal>&&</literal> and <literal>AND</literal>.
- Because of this nice syntax, MySQL Server doesn't support the
- standard SQL <literal>||</literal> operator for string
- concatenation; use <literal>CONCAT()</literal> instead. Because
- <literal>CONCAT()</literal> takes any number of arguments, it's
- easy to convert use of the <literal>||</literal> operator to
- MySQL Server.
- </para></listitem>
+ <listitem><para>
+ MySQL Server understands the <literal>||</literal> and
+ <literal>&&</literal> operators to mean logical OR and
+ AND, as in the C programming language. In MySQL Server,
+ <literal>||</literal> and <literal>OR</literal> are synonyms, as
+ are <literal>&&</literal> and <literal>AND</literal>.
+ Because of this nice syntax, MySQL Server doesn't support the
+ standard SQL <literal>||</literal> operator for string
+ concatenation; use <literal>CONCAT()</literal> instead. Because
+ <literal>CONCAT()</literal> takes any number of arguments, it's
+ easy to convert use of the <literal>||</literal> operator to MySQL
+ Server.
+ </para></listitem>
- <listitem><para>
- Use of <literal>COUNT(DISTINCT list)</literal> where
- <literal>list</literal> has more than one element.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>COUNT(DISTINCT list)</literal> where
+ <literal>list</literal> has more than one element.
+ </para></listitem>
- <listitem><para>
- All string comparisons are case-insensitive by default, with sort
- ordering determined by the current character set (ISO-8859-1
- Latin1 by default). If you don't like this, you should declare
- your columns with the <literal>BINARY</literal> attribute or use
- the <literal>BINARY</literal> cast, which causes comparisons to
- be done using the underlying character code values rather then a
- lexical ordering.
- </para>
+ <listitem><para>
+ All string comparisons are case-insensitive by default, with sort
+ ordering determined by the current character set (ISO-8859-1
+ Latin1 by default). If you don't like this, you should declare
+ your columns with the <literal>BINARY</literal> attribute or use
+ the <literal>BINARY</literal> cast, which causes comparisons to be
+ done using the underlying character code values rather then a
+ lexical ordering.
+ </para>
- <indexterm type="concept">
- <primary>PostgreSQL compatibility</primary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>compatibility</primary>
- <secondary>with PostgreSQL</secondary>
- </indexterm></listitem>
-
- <listitem><para>
- The <literal>%</literal> operator is a synonym for
- <literal>MOD()</literal>. That is, <literal>N % M</literal> is
- equivalent to <literal>MOD(N,M)</literal>. <literal>%</literal>
- is supported for C programmers and for compatibility with
- PostgreSQL.
- </para></listitem>
+ <indexterm type="concept">
+ <primary>PostgreSQL compatibility</primary>
+ </indexterm>
- <listitem><para>
- The <literal>=</literal>, <literal><></literal>,
- <literal><=</literal> ,<literal><</literal>,
- <literal>>=</literal>,<literal>></literal>,
- <literal><<</literal>, <literal>>></literal>,
- <literal><=></literal>, <literal>AND</literal>,
- <literal>OR</literal>, or <literal>LIKE</literal> operators may
- be used in column comparisons to the left of the
- <literal>FROM</literal> in <literal>SELECT</literal> statements.
- For example:
- </para>
+ <indexterm type="concept">
+ <primary>compatibility</primary>
+ <secondary>with PostgreSQL</secondary>
+ </indexterm></listitem>
+
+ <listitem><para>
+ The <literal>%</literal> operator is a synonym for
+ <literal>MOD()</literal>. That is, <literal>N % M</literal> is
+ equivalent to <literal>MOD(N,M)</literal>. <literal>%</literal> is
+ supported for C programmers and for compatibility with PostgreSQL.
+ </para></listitem>
+
+ <listitem><para>
+ The <literal>=</literal>, <literal><></literal>,
+ <literal><=</literal> ,<literal><</literal>,
+ <literal>>=</literal>,<literal>></literal>,
+ <literal><<</literal>, <literal>>></literal>,
+ <literal><=></literal>, <literal>AND</literal>,
+ <literal>OR</literal>, or <literal>LIKE</literal> operators may be
+ used in column comparisons to the left of the
+ <literal>FROM</literal> in <literal>SELECT</literal> statements.
+ For example:
+ </para>
<programlisting>
mysql> SELECT col1=1 AND col2=2 FROM <replaceable>tbl_name</replaceable>;
</programlisting></listitem>
- <listitem><para>
- The <literal>LAST_INSERT_ID()</literal> function that returns the
- most recent <literal>AUTO_INCREMENT</literal> value. See
- <xref linkend="information-functions"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>LAST_INSERT_ID()</literal> function that returns the
+ most recent <literal>AUTO_INCREMENT</literal> value. See
+ <xref linkend="information-functions"/>.
+ </para></listitem>
- <listitem><para>
- <literal>LIKE</literal> is allowed on numeric columns.
- </para></listitem>
+ <listitem><para>
+ <literal>LIKE</literal> is allowed on numeric columns.
+ </para></listitem>
- <listitem><para>
- The <literal>REGEXP</literal> and <literal>NOT REGEXP</literal>
- extended regular expression operators.
- </para></listitem>
+ <listitem><para>
+ The <literal>REGEXP</literal> and <literal>NOT REGEXP</literal>
+ extended regular expression operators.
+ </para></listitem>
- <listitem><para>
- <literal>CONCAT()</literal> or <literal>CHAR()</literal> with one
- argument or more than two arguments. (In MySQL Server, these
- functions can take any number of arguments.)
- </para></listitem>
+ <listitem><para>
+ <literal>CONCAT()</literal> or <literal>CHAR()</literal> with one
+ argument or more than two arguments. (In MySQL Server, these
+ functions can take any number of arguments.)
+ </para></listitem>
- <listitem><para>
- The <literal>BIT_COUNT()</literal>, <literal>CASE</literal>,
- <literal>ELT()</literal>, <literal>FROM_DAYS()</literal>,
- <literal>FORMAT()</literal>, <literal>IF()</literal>,
- <literal>PASSWORD()</literal>, <literal>ENCRYPT()</literal>,
- <literal>MD5()</literal>, <literal>ENCODE()</literal>,
- <literal>DECODE()</literal>, <literal>PERIOD_ADD()</literal>,
- <literal>PERIOD_DIFF()</literal>, <literal>TO_DAYS()</literal>,
- and <literal>WEEKDAY()</literal> functions.
- </para></listitem>
+ <listitem><para>
+ The <literal>BIT_COUNT()</literal>, <literal>CASE</literal>,
+ <literal>ELT()</literal>, <literal>FROM_DAYS()</literal>,
+ <literal>FORMAT()</literal>, <literal>IF()</literal>,
+ <literal>PASSWORD()</literal>, <literal>ENCRYPT()</literal>,
+ <literal>MD5()</literal>, <literal>ENCODE()</literal>,
+ <literal>DECODE()</literal>, <literal>PERIOD_ADD()</literal>,
+ <literal>PERIOD_DIFF()</literal>, <literal>TO_DAYS()</literal>,
+ and <literal>WEEKDAY()</literal> functions.
+ </para></listitem>
- <listitem><para>
- Use of <literal>TRIM()</literal> to trim substrings. Standard SQL
- supports removal of single characters only.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>TRIM()</literal> to trim substrings. Standard SQL
+ supports removal of single characters only.
+ </para></listitem>
- <listitem><para>
- The <literal>GROUP BY</literal> functions
- <literal>STD()</literal>, <literal>BIT_OR()</literal>,
- <literal>BIT_AND()</literal>, <literal>BIT_XOR()</literal>, and
- <literal>GROUP_CONCAT()</literal>. See
- <xref linkend="group-by-functions-and-modifiers"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>GROUP BY</literal> functions
+ <literal>STD()</literal>, <literal>BIT_OR()</literal>,
+ <literal>BIT_AND()</literal>, <literal>BIT_XOR()</literal>, and
+ <literal>GROUP_CONCAT()</literal>. See
+ <xref linkend="group-by-functions-and-modifiers"/>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
</itemizedlist>
@@ -4033,9 +4030,9 @@
supports transactions with the <literal>InnoDB</literal> and
<literal>BDB</literal> transactional storage engines.
<literal>InnoDB</literal> provides <emphasis>full</emphasis>
- <literal>ACID</literal> compliance. MySQL Cluster is also a
- transaction-safe storage engine. See
- <xref linkend="storage-engines"/>.
+ <literal>ACID</literal> compliance. MySQL Cluster is also a
+ transaction-safe storage engine. See
+ <xref linkend="storage-engines"/>.
</para>
<para>
@@ -4685,7 +4682,7 @@
<para>
You can get information about the number of rows actually inserted
or updated with the <literal>mysql_info()</literal> C API function.
- See <xref linkend="mysql-info"/>. In MySQL 4.1, you can also use
+ See <xref linkend="mysql-info"/>. In MySQL 4.1, you can also use
the <literal>SHOW WARNINGS</literal> statement. See
<xref linkend="show-warnings"/>.
</para>
@@ -4809,10 +4806,10 @@
<para>
<literal>ENUM</literal> and <literal>SET</literal> columns provide
an efficient way to define columns that can contain only a given
- set of values. However, in MySQL 4.1 and earlier,
- <literal>ENUM</literal> and <literal>SET</literal> are not true
- constraints. This is for the same reasons that
- <literal>NOT NULL</literal> is not honored. See
+ set of values. However, in MySQL 4.1 and earlier,
+ <literal>ENUM</literal> and <literal>SET</literal> are not true
+ constraints. This is for the same reasons that <literal>NOT
+ NULL</literal> is not honored. See
<xref linkend="constraint-invalid-data"/>.
</para>
@@ -4839,7 +4836,7 @@
assign <literal>'a,x,b,y'</literal> results in a value of
<literal>'a,b'</literal>. See <xref linkend="set"/>.
</para>
-
+
</section>
</section>
--- 1.11/refman-5.0/introduction.xml 2005-07-11 15:35:08 -05:00
+++ 1.12/refman-5.0/introduction.xml 2005-07-11 15:36:47 -05:00
@@ -147,20 +147,20 @@
<!-- NOTE: Next para also appears in preface.xml -->
<para>
- This is the Reference Manual for the MySQL Database System, Version
+ This is the Reference Manual for the MySQL Database System, Version
5.0, up to Release ¤t-version;. It is not intended for use with
- older versions of the MySQL software due to the many functional and
- other differences between MySQL 5.0 and previous versions.
-
- <!-- TODO: Update next sentence with a link when it's been
+ older versions of the MySQL software due to the many functional and
+ other differences between MySQL 5.0 and previous versions.
+
+<!-- TODO: Update next sentence with a link when it's been
determined how this should be handled. Likely to be something
like http://dev.mysql.com/doc/en/4-1/ ? -->
-
- If you are using an earlier release of the MySQL software, please
- refer to the <citetitle>&title-refman-previous;</citetitle>, which
- provides coverage of the 3.22, 3.23, 4.0, and 4.1 series of MySQL
- software releases. Differences between minor versions of MySQL 5.0
- are noted in the present text with reference to release numbers
+
+ If you are using an earlier release of the MySQL software, please
+ refer to the <citetitle>&title-refman-previous;</citetitle>, which
+ provides coverage of the 3.22, 3.23, 4.0, and 4.1 series of MySQL
+ software releases. Differences between minor versions of MySQL 5.0
+ are noted in the present text with reference to release numbers
(5.0.<replaceable>x</replaceable>).
</para>
@@ -190,13 +190,14 @@
</indexterm>
<para>
- The base format for all MySQL documentation consists of a set of
- <ulink url="http://docbook.org/">DocBook XML</ulink> files. HTML and
- other formats are produced from these automatically using, among
+ The base format for all MySQL documentation consists of a set of
+ <ulink url="http://docbook.org/">DocBook XML</ulink> files. HTML and
+ other formats are produced from these automatically using, among
other tools, the
- <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/reference.html">DocBook
+ <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/reference.html">DocBook
XSL stylesheets</ulink>.
- <!-- [SH] We might want to add details about creating CHM, PDF, INFO, ... -->
+
+<!-- [SH] We might want to add details about creating CHM, PDF, INFO, ... -->
</para>
<para>
@@ -208,17 +209,17 @@
<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
+ consisting of Paul DuBois, Stefan Hinz, Mike Hillyer, and Jon
+ Stephens. For the many other contributors, see
<xref linkend="credits"/>.
</para>
<para>
- The copyright to this manual is owned by the Swedish company
- MySQL AB. MySQL® and the MySQL logo are registered trademarks of
- MySQL AB. Other trademarks and registered trademarks referred to in
- this manual are the property of their respective owners, and are used
- for identification purposes only.
+ The copyright to this manual is owned by the Swedish company MySQL
+ AB. MySQL® and the MySQL logo are registered trademarks of MySQL
+ AB. Other trademarks and registered trademarks referred to in this
+ manual are the property of their respective owners, and are used for
+ identification purposes only.
</para>
</section>
@@ -770,10 +771,10 @@
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.
+ 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>
@@ -1028,7 +1029,7 @@
</para></listitem>
<listitem><para>
- In MySQL 5.0, Windows servers also support shared-memory
+ In MySQL 5.0, Windows servers also support shared-memory
connections if started with the
<literal>--shared-memory</literal> option. Clients can connect
through shared memory by using the
@@ -1138,7 +1139,7 @@
</para>
<para>
- The original codebase stems back to the early 1980s. At TcX, the
+ The original codebase stems back to the early 1980s. At TcX, the
predecessor of MySQL AB, MySQL code has worked in projects since
mid-1996, without any problems. When the MySQL Database Software
initially was released to a wider public, our new users quickly
@@ -1186,7 +1187,7 @@
</para>
<para>
- The <literal>InnoDB</literal> transactional storage engine is
+ The <literal>InnoDB</literal> transactional storage engine is
stable and is being used in large, heavy-load production systems.
</para></listitem>
@@ -1256,10 +1257,10 @@
</indexterm>
<para>
- In MySQL 5.0, using the <literal>MyISAM</literal> storage engine,
- the maximum size of tables is 65536 terabytes (256 ^ 7 - 1 bytes).
- Thus, the maximum effective table size for MySQL databases is
- usually determined by operating system constraints on file sizes,
+ In MySQL 5.0, using the <literal>MyISAM</literal> storage engine,
+ the maximum size of tables is 65536 terabytes (256 ^ 7 - 1 bytes).
+ Thus, the maximum effective table size for MySQL databases is
+ usually determined by operating system constraints on file sizes,
and not by MySQL's internal limitations.
</para>
@@ -1355,12 +1356,12 @@
<para>
On Linux 2.2, you can get <literal>MyISAM</literal> tables larger
than 2GB in size by using the Large File Support (LFS) patch for the
- ext2 filesystem. On Linux 2.4 and later, patches also exist for
+ ext2 filesystem. On Linux 2.4 and later, patches also exist for
ReiserFS supporting big files (up to 2TB). Most current Linux
- distributions are based on kernel 2.4 or 2.6 and include all the
- required LFS patches. With JFS and XFS, petabyte and larger files
- are possible on Linux. However, the maximum available file size
- still depends on several factors, one of them being the filesystem
+ distributions are based on kernel 2.4 or 2.6 and include all the
+ required LFS patches. With JFS and XFS, petabyte and larger files
+ are possible on Linux. However, the maximum available file size
+ still depends on several factors, one of them being the filesystem
used to store MySQL tables.
</para>
@@ -1410,9 +1411,7 @@
least 50%, so you can have, in effect, much bigger tables.
<command>myisampack</command> also can merge multiple tables into a
single table. See <xref linkend="myisampack"/>.
- </para>
-
- </listitem>
+ </para></listitem>
<listitem><para>
MySQL includes a <literal>MERGE</literal> library that allows you
@@ -1465,8 +1464,8 @@
</para></listitem>
<listitem><para>
- In MySQL 5.0 and later, the <literal>YEAR</literal> column type
- can store years <literal>0</literal> and <literal>1901</literal> to
+ In MySQL 5.0 and later, the <literal>YEAR</literal> column type can
+ store years <literal>0</literal> and <literal>1901</literal> to
<literal>2155</literal> in one byte and display them using two or
four digits. All two-digit years are considered to be in the range
<literal>1970</literal> to <literal>2069</literal>, which means
@@ -1582,20 +1581,22 @@
</para>
<para>
- <!-- TODO: Fix this sentence once 5.0 is ready for production -->
+<!-- TODO: Fix this sentence once 5.0 is ready for production -->
+
The current production release series is MySQL 5.0, which was
declared stable for production use as of Version 5.0.9, released in
August 2005. The previous production release series is MySQL 4.1,
which was declared stable for production use as of Version 4.1.7,
released in October 2004. Production status means that future 5.0 and
- 4.1 development is limited only to bugfixes. For the older MySQL 4.0
+ 4.1 development is limited only to bugfixes. For the older MySQL 4.0
and 3.23 series, only critical bugfixes are made.
</para>
<para>
Active MySQL development currently is taking place in the MySQL 5.1
release series, this means that new features are being added there.
- <!--
+
+<!--
MySQL 5.1 is available in alpha status.
-->
</para>
@@ -1706,66 +1707,64 @@
</tbody>
</tgroup>
</informaltable>
-
-
+
<section id="nutshell-embedded-mysql">
-
- <title id='title-nutshell-embedded-mysql'>&title-nutshell-embedded-mysql;</title>
-
- <para>
- The <literal>libmysqld</literal> embedded server library makes
- MySQL Server suitable for a vastly expanded realm of applications.
- By using this library, developers can embed MySQL Server into
- various applications and electronics devices, where the end user
- has no knowledge of there actually being an underlying database.
- Embedded MySQL Server is ideal for use behind the scenes in
- Internet appliances, public kiosks, turnkey hardware/software
- combination units, high performance Internet servers,
- self-contained databases distributed on CD-ROM, and so on.
- </para>
-
- <para>
- Many users of <literal>libmysqld</literal> benefit from the MySQL
- Dual Licensing. For those not wishing to be bound by the GPL, the
- software is also made available under a commercial license. See
- <ulink url="http://www.mysql.com/company/legal/licensing/">http://www.mysql.com/company/legal/licensing/</ulink>
- for more information on the licensing policy of MySQL AB. The
- embedded MySQL library uses the same interface as the normal client
- library, so it is convenient and easy to use. See
- <xref linkend="libmysqld"/>.
- </para>
-
- <para>
- On Windows there are two different libraries:
- </para>
-
- <informaltable>
- <tgroup cols="2">
- <colspec colwidth="30*"/>
- <colspec colwidth="60*"/>
- <tbody>
- <row>
- <entry>
- <literal>libmysqld.lib</literal>
- </entry>
- <entry>
- Dynamic library for threaded applications.
- </entry>
- </row>
- <row>
- <entry>
- <literal>mysqldemb.lib</literal>
- </entry>
- <entry>
- Static library for not threaded applications.
- </entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- </section>
+ <title id='title-nutshell-embedded-mysql'>&title-nutshell-embedded-mysql;</title>
+
+ <para>
+ The <literal>libmysqld</literal> embedded server library makes MySQL
+ Server suitable for a vastly expanded realm of applications. By
+ using this library, developers can embed MySQL Server into various
+ applications and electronics devices, where the end user has no
+ knowledge of there actually being an underlying database. Embedded
+ MySQL Server is ideal for use behind the scenes in Internet
+ appliances, public kiosks, turnkey hardware/software combination
+ units, high performance Internet servers, self-contained databases
+ distributed on CD-ROM, and so on.
+ </para>
+
+ <para>
+ Many users of <literal>libmysqld</literal> benefit from the MySQL
+ Dual Licensing. For those not wishing to be bound by the GPL, the
+ software is also made available under a commercial license. See
+ <ulink url="http://www.mysql.com/company/legal/licensing/">http://www.mysql.com/company/legal/licensing/</ulink>
+ for more information on the licensing policy of MySQL AB. The
+ embedded MySQL library uses the same interface as the normal client
+ library, so it is convenient and easy to use. See
+ <xref linkend="libmysqld"/>.
+ </para>
+
+ <para>
+ On Windows there are two different libraries:
+ </para>
+
+ <informaltable>
+ <tgroup cols="2">
+ <colspec colwidth="30*"/>
+ <colspec colwidth="60*"/>
+ <tbody>
+ <row>
+ <entry>
+ <literal>libmysqld.lib</literal>
+ </entry>
+ <entry>
+ Dynamic library for threaded applications.
+ </entry>
+ </row>
+ <row>
+ <entry>
+ <literal>mysqldemb.lib</literal>
+ </entry>
+ <entry>
+ Static library for not threaded applications.
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </informaltable>
+
+ </section>
<section id="mysql-5-0-nutshell">
@@ -1773,36 +1772,36 @@
<para>
New features in MySQL 5.0 include the following:
- </para>
-
- <itemizedlist>
-
- <listitem>
- <para><link linkend="stored-procedures">&title-stored-procedures;</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="views">&title-views;</link> (including updatable
- views)</para>
- </listitem>
-
- <listitem>
- <para>Rudimentary <link linkend="triggers">&title-triggers;</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="information-schema">&title-information-schema;</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="precision-math">&title-precision-math;</link></para>
- </listitem>
-
- </itemizedlist>
-
+ </para>
+
+ <itemizedlist>
+
+ <listitem><para>
+ <link linkend="stored-procedures">&title-stored-procedures;</link>
+ </para></listitem>
+
+ <listitem><para>
+ <link linkend="views">&title-views;</link> (including updatable
+ views)
+ </para></listitem>
+
+ <listitem><para>
+ Rudimentary <link linkend="triggers">&title-triggers;</link>
+ </para></listitem>
+
+ <listitem><para>
+ <link linkend="information-schema">&title-information-schema;</link>
+ </para></listitem>
+
+ <listitem><para>
+ <link linkend="precision-math">&title-precision-math;</link>
+ </para></listitem>
+
+ </itemizedlist>
+
<para>
For those wishing to take a look at the bleeding edge of MySQL
- development, we make our BitKeeper repository for MySQL publicly
+ development, we make our BitKeeper repository for MySQL publicly
available. See <xref linkend="installing-source-tree"/>.
</para>
@@ -3096,45 +3095,45 @@
database directory. This has a few implications:
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><indexterm type="concept">
- <primary>database names</primary>
- <secondary>case-sensitivity</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>case-sensitivity</primary>
- <secondary>of database names</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>table names</primary>
- <secondary>case-sensitivity</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>case-sensitivity</primary>
- <secondary>of table names</secondary>
- </indexterm>
-
- <para>
- Database names and table names are case sensitive in MySQL Server
- on operating systems that have case-sensitive filenames (such as
- most Unix systems). See <xref linkend="name-case-sensitivity"/>.
- </para></listitem>
+ <listitem><indexterm type="concept">
+ <primary>database names</primary>
+ <secondary>case-sensitivity</secondary>
+ </indexterm>
+
+ <indexterm type="concept">
+ <primary>case-sensitivity</primary>
+ <secondary>of database names</secondary>
+ </indexterm>
+
+ <indexterm type="concept">
+ <primary>table names</primary>
+ <secondary>case-sensitivity</secondary>
+ </indexterm>
+
+ <indexterm type="concept">
+ <primary>case-sensitivity</primary>
+ <secondary>of table names</secondary>
+ </indexterm>
+
+ <para>
+ Database names and table names are case sensitive in MySQL Server
+ on operating systems that have case-sensitive filenames (such as
+ most Unix systems). See <xref linkend="name-case-sensitivity"/>.
+ </para></listitem>
- <listitem><para>
- You can use standard system commands to back up, rename, move,
- delete, and copy tables that are managed by the
- <literal>MyISAM</literal> or <literal>ISAM</literal> storage
- engines. For example, to rename a <literal>MyISAM</literal>
- table, rename the <filename>.MYD</filename>,
- <filename>.MYI</filename>, and <filename>.frm</filename> files to
- which the table corresponds.
- </para></listitem>
+ <listitem><para>
+ You can use standard system commands to back up, rename, move,
+ delete, and copy tables that are managed by the
+ <literal>MyISAM</literal> or <literal>ISAM</literal> storage
+ engines. For example, to rename a <literal>MyISAM</literal> table,
+ rename the <filename>.MYD</filename>, <filename>.MYI</filename>,
+ and <filename>.frm</filename> files to which the table
+ corresponds.
+ </para></listitem>
- </itemizedlist>
+ </itemizedlist>
<para>
Database, table, index, column, or alias names may begin with a
@@ -3145,334 +3144,326 @@
General language syntax
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- Strings may be enclosed by either '<literal>"</literal>' or
- '<literal>'</literal>', not just by '<literal>'</literal>'.
- </para></listitem>
+ <listitem><para>
+ Strings may be enclosed by either '<literal>"</literal>' or
+ '<literal>'</literal>', not just by '<literal>'</literal>'.
+ </para></listitem>
- <listitem><para>
- Use of '<literal>\</literal>' as an escape character in strings.
- </para></listitem>
+ <listitem><para>
+ Use of '<literal>\</literal>' as an escape character in strings.
+ </para></listitem>
- <listitem><para>
- In SQL statements, you can access tables from different databases
- with the <replaceable>db_name.tbl_name</replaceable> syntax. Some
- SQL servers provide the same functionality but call this
- <literal>User space</literal>. MySQL Server doesn't support
- tablespaces such as used in statements like this: <literal>CREATE
- TABLE ralph.my_table...IN my_tablespace</literal>.
- </para></listitem>
+ <listitem><para>
+ In SQL statements, you can access tables from different databases
+ with the <replaceable>db_name.tbl_name</replaceable> syntax. Some
+ SQL servers provide the same functionality but call this
+ <literal>User space</literal>. MySQL Server doesn't support
+ tablespaces such as used in statements like this: <literal>CREATE
+ TABLE ralph.my_table...IN my_tablespace</literal>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
SQL statement syntax
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- The <literal>ANALYZE TABLE</literal>, <literal>CHECK
- TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and
- <literal>REPAIR TABLE</literal> statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>ANALYZE TABLE</literal>, <literal>CHECK
+ TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and
+ <literal>REPAIR TABLE</literal> statements.
+ </para></listitem>
- <listitem><para>
- The <literal>CREATE DATABASE</literal> and <literal>DROP
- DATABASE</literal> statements. See
- <xref linkend="create-database"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>CREATE DATABASE</literal> and <literal>DROP
+ DATABASE</literal> statements. See
+ <xref linkend="create-database"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>DO</literal> statement.
- </para></listitem>
+ <listitem><para>
+ The <literal>DO</literal> statement.
+ </para></listitem>
- <listitem><para>
- <literal>EXPLAIN SELECT</literal> to get a description of how
- tables are joined.
- </para></listitem>
+ <listitem><para>
+ <literal>EXPLAIN SELECT</literal> to get a description of how
+ tables are joined.
+ </para></listitem>
- <listitem><para>
- The <literal>FLUSH</literal> and <literal>RESET</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>FLUSH</literal> and <literal>RESET</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- The <literal>SET</literal> statement. See
- <xref linkend="set-option"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>SET</literal> statement. See
+ <xref linkend="set-option"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>SHOW</literal> statement. See
- <xref linkend="show"/>.
- </para>
+ <listitem><para>
+ The <literal>SHOW</literal> statement. See <xref linkend="show"/>.
+ </para>
- <indexterm type="concept">
- <primary>Oracle compatibility</primary>
- </indexterm>
+ <indexterm type="concept">
+ <primary>Oracle compatibility</primary>
+ </indexterm>
- <indexterm type="concept">
- <primary>compatibility</primary>
- <secondary>with Oracle</secondary>
- </indexterm></listitem>
+ <indexterm type="concept">
+ <primary>compatibility</primary>
+ <secondary>with Oracle</secondary>
+ </indexterm></listitem>
- <listitem><para>
- Use of <literal>LOAD DATA INFILE</literal>. In many cases, this
- syntax is compatible with Oracle's <literal>LOAD DATA
- INFILE</literal>. See <xref linkend="load-data"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>LOAD DATA INFILE</literal>. In many cases, this
+ syntax is compatible with Oracle's <literal>LOAD DATA
+ INFILE</literal>. See <xref linkend="load-data"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>RENAME TABLE</literal>. See
- <xref linkend="rename-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>RENAME TABLE</literal>. See
+ <xref linkend="rename-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>REPLACE</literal> instead of
- <literal>DELETE</literal> + <literal>INSERT</literal>. See
- <xref linkend="replace"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>REPLACE</literal> instead of
+ <literal>DELETE</literal> + <literal>INSERT</literal>. See
+ <xref linkend="replace"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>CHANGE col_name</literal>, <literal>DROP
- col_name</literal>, or <literal>DROP INDEX</literal>,
- <literal>IGNORE</literal> or <literal>RENAME</literal> in an
- <literal>ALTER TABLE</literal> statement. Use of multiple
- <literal>ADD</literal>, <literal>ALTER</literal>,
- <literal>DROP</literal>, or <literal>CHANGE</literal> clauses in
- an <literal>ALTER TABLE</literal> statement. See
- <xref linkend="alter-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>CHANGE col_name</literal>, <literal>DROP
+ col_name</literal>, or <literal>DROP INDEX</literal>,
+ <literal>IGNORE</literal> or <literal>RENAME</literal> in an
+ <literal>ALTER TABLE</literal> statement. Use of multiple
+ <literal>ADD</literal>, <literal>ALTER</literal>,
+ <literal>DROP</literal>, or <literal>CHANGE</literal> clauses in
+ an <literal>ALTER TABLE</literal> statement. See
+ <xref linkend="alter-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of index names, indexes on a prefix of a field, and use of
- <literal>INDEX</literal> or <literal>KEY</literal> in a
- <literal>CREATE TABLE</literal> statement. See
- <xref linkend="create-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of index names, indexes on a prefix of a field, and use of
+ <literal>INDEX</literal> or <literal>KEY</literal> in a
+ <literal>CREATE TABLE</literal> statement. See
+ <xref linkend="create-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>TEMPORARY</literal> or <literal>IF NOT
- EXISTS</literal> with <literal>CREATE TABLE</literal>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>TEMPORARY</literal> or <literal>IF NOT
+ EXISTS</literal> with <literal>CREATE TABLE</literal>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>IF EXISTS</literal> with <literal>DROP
- TABLE</literal>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>IF EXISTS</literal> with <literal>DROP
+ TABLE</literal>.
+ </para></listitem>
- <listitem><para>
- You can drop multiple tables with a single <literal>DROP
- TABLE</literal> statement.
- </para></listitem>
+ <listitem><para>
+ You can drop multiple tables with a single <literal>DROP
+ TABLE</literal> statement.
+ </para></listitem>
- <listitem><para>
- The <literal>ORDER BY</literal> and <literal>LIMIT</literal>
- clauses of the <literal>UPDATE</literal> and
- <literal>DELETE</literal> statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>ORDER BY</literal> and <literal>LIMIT</literal>
+ clauses of the <literal>UPDATE</literal> and
+ <literal>DELETE</literal> statements.
+ </para></listitem>
- <listitem><para>
- <literal>INSERT INTO ... SET col_name = ...</literal> syntax.
- </para></listitem>
+ <listitem><para>
+ <literal>INSERT INTO ... SET col_name = ...</literal> syntax.
+ </para></listitem>
- <listitem><para>
- The <literal>DELAYED</literal> clause of the
- <literal>INSERT</literal> and <literal>REPLACE</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>DELAYED</literal> clause of the
+ <literal>INSERT</literal> and <literal>REPLACE</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- The <literal>LOW_PRIORITY</literal> clause of the
- <literal>INSERT</literal>, <literal>REPLACE</literal>,
- <literal>DELETE</literal>, and <literal>UPDATE</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>LOW_PRIORITY</literal> clause of the
+ <literal>INSERT</literal>, <literal>REPLACE</literal>,
+ <literal>DELETE</literal>, and <literal>UPDATE</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- Use of <literal>INTO OUTFILE</literal> and
- <literal>STRAIGHT_JOIN</literal> in a <literal>SELECT</literal>
- statement. See <xref linkend="select"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>INTO OUTFILE</literal> and
+ <literal>STRAIGHT_JOIN</literal> in a <literal>SELECT</literal>
+ statement. See <xref linkend="select"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>SQL_SMALL_RESULT</literal> option in a
- <literal>SELECT</literal> statement.
- </para></listitem>
+ <listitem><para>
+ The <literal>SQL_SMALL_RESULT</literal> option in a
+ <literal>SELECT</literal> statement.
+ </para></listitem>
- <listitem><para>
- You don't need to name all selected columns in the <literal>GROUP
- BY</literal> part. This gives better performance for some very
- specific, but quite normal queries. See
- <xref linkend="group-by-functions-and-modifiers"/>.
- </para></listitem>
+ <listitem><para>
+ You don't need to name all selected columns in the <literal>GROUP
+ BY</literal> part. This gives better performance for some very
+ specific, but quite normal queries. See
+ <xref linkend="group-by-functions-and-modifiers"/>.
+ </para></listitem>
- <listitem><para>
- You can specify <literal>ASC</literal> and
- <literal>DESC</literal> with <literal>GROUP BY</literal>.
- </para></listitem>
+ <listitem><para>
+ You can specify <literal>ASC</literal> and <literal>DESC</literal>
+ with <literal>GROUP BY</literal>.
+ </para></listitem>
- <listitem><para>
- The ability to set variables in a statement with the
- <literal>:=</literal> assignment operator:
+ <listitem><para>
+ The ability to set variables in a statement with the
+ <literal>:=</literal> assignment operator:
<programlisting>
mysql> SELECT @a:=SUM(total),@b=COUNT(*),@a/@b AS avg
-> FROM test_table;
mysql> SELECT @t1:=(@t2:=1)+@t3:=4,@t1,@t2,@t3;
</programlisting>
- </para></listitem>
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
Column types
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- The column types <literal>MEDIUMINT</literal>,
- <literal>SET</literal>, <literal>ENUM</literal>, and the
- different <literal>BLOB</literal> and <literal>TEXT</literal>
- types.
- </para></listitem>
+ <listitem><para>
+ The column types <literal>MEDIUMINT</literal>,
+ <literal>SET</literal>, <literal>ENUM</literal>, and the different
+ <literal>BLOB</literal> and <literal>TEXT</literal> types.
+ </para></listitem>
- <listitem><para>
- The column attributes <literal>AUTO_INCREMENT</literal>,
- <literal>BINARY</literal>, <literal>NULL</literal>,
- <literal>UNSIGNED</literal>, and <literal>ZEROFILL</literal>.
- </para></listitem>
+ <listitem><para>
+ The column attributes <literal>AUTO_INCREMENT</literal>,
+ <literal>BINARY</literal>, <literal>NULL</literal>,
+ <literal>UNSIGNED</literal>, and <literal>ZEROFILL</literal>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
Functions and operators
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- To make it easier for users who come from other SQL environments,
- MySQL Server supports aliases for many functions. For example,
- all string functions support both standard SQL syntax and ODBC
- syntax.
- </para></listitem>
+ <listitem><para>
+ To make it easier for users who come from other SQL environments,
+ MySQL Server supports aliases for many functions. For example, all
+ string functions support both standard SQL syntax and ODBC syntax.
+ </para></listitem>
- <listitem><para>
- MySQL Server understands the <literal>||</literal> and
- <literal>&&</literal> operators to mean logical OR and
- AND, as in the C programming language. In MySQL Server,
- <literal>||</literal> and <literal>OR</literal> are synonyms, as
- are <literal>&&</literal> and <literal>AND</literal>.
- Because of this nice syntax, MySQL Server doesn't support the
- standard SQL <literal>||</literal> operator for string
- concatenation; use <literal>CONCAT()</literal> instead. Because
- <literal>CONCAT()</literal> takes any number of arguments, it's
- easy to convert use of the <literal>||</literal> operator to
- MySQL Server.
- </para></listitem>
+ <listitem><para>
+ MySQL Server understands the <literal>||</literal> and
+ <literal>&&</literal> operators to mean logical OR and
+ AND, as in the C programming language. In MySQL Server,
+ <literal>||</literal> and <literal>OR</literal> are synonyms, as
+ are <literal>&&</literal> and <literal>AND</literal>.
+ Because of this nice syntax, MySQL Server doesn't support the
+ standard SQL <literal>||</literal> operator for string
+ concatenation; use <literal>CONCAT()</literal> instead. Because
+ <literal>CONCAT()</literal> takes any number of arguments, it's
+ easy to convert use of the <literal>||</literal> operator to MySQL
+ Server.
+ </para></listitem>
- <listitem><para>
- Use of <literal>COUNT(DISTINCT list)</literal> where
- <literal>list</literal> has more than one element.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>COUNT(DISTINCT list)</literal> where
+ <literal>list</literal> has more than one element.
+ </para></listitem>
- <listitem><para>
- All string comparisons are case-insensitive by default, with sort
- ordering determined by the current character set (ISO-8859-1
- Latin1 by default). If you don't like this, you should declare
- your columns with the <literal>BINARY</literal> attribute or use
- the <literal>BINARY</literal> cast, which causes comparisons to
- be done using the underlying character code values rather then a
- lexical ordering.
- </para>
+ <listitem><para>
+ All string comparisons are case-insensitive by default, with sort
+ ordering determined by the current character set (ISO-8859-1
+ Latin1 by default). If you don't like this, you should declare
+ your columns with the <literal>BINARY</literal> attribute or use
+ the <literal>BINARY</literal> cast, which causes comparisons to be
+ done using the underlying character code values rather then a
+ lexical ordering.
+ </para>
- <indexterm type="concept">
- <primary>PostgreSQL compatibility</primary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>compatibility</primary>
- <secondary>with PostgreSQL</secondary>
- </indexterm></listitem>
-
- <listitem><para>
- The <literal>%</literal> operator is a synonym for
- <literal>MOD()</literal>. That is, <literal>N % M</literal> is
- equivalent to <literal>MOD(N,M)</literal>. <literal>%</literal>
- is supported for C programmers and for compatibility with
- PostgreSQL.
- </para></listitem>
+ <indexterm type="concept">
+ <primary>PostgreSQL compatibility</primary>
+ </indexterm>
- <listitem><para>
- The <literal>=</literal>, <literal><></literal>,
- <literal><=</literal> ,<literal><</literal>,
- <literal>>=</literal>,<literal>></literal>,
- <literal><<</literal>, <literal>>></literal>,
- <literal><=></literal>, <literal>AND</literal>,
- <literal>OR</literal>, or <literal>LIKE</literal> operators may
- be used in column comparisons to the left of the
- <literal>FROM</literal> in <literal>SELECT</literal> statements.
- For example:
- </para>
+ <indexterm type="concept">
+ <primary>compatibility</primary>
+ <secondary>with PostgreSQL</secondary>
+ </indexterm></listitem>
+
+ <listitem><para>
+ The <literal>%</literal> operator is a synonym for
+ <literal>MOD()</literal>. That is, <literal>N % M</literal> is
+ equivalent to <literal>MOD(N,M)</literal>. <literal>%</literal> is
+ supported for C programmers and for compatibility with PostgreSQL.
+ </para></listitem>
+
+ <listitem><para>
+ The <literal>=</literal>, <literal><></literal>,
+ <literal><=</literal> ,<literal><</literal>,
+ <literal>>=</literal>,<literal>></literal>,
+ <literal><<</literal>, <literal>>></literal>,
+ <literal><=></literal>, <literal>AND</literal>,
+ <literal>OR</literal>, or <literal>LIKE</literal> operators may be
+ used in column comparisons to the left of the
+ <literal>FROM</literal> in <literal>SELECT</literal> statements.
+ For example:
+ </para>
<programlisting>
mysql> SELECT col1=1 AND col2=2 FROM <replaceable>tbl_name</replaceable>;
</programlisting></listitem>
- <listitem><para>
- The <literal>LAST_INSERT_ID()</literal> function that returns the
- most recent <literal>AUTO_INCREMENT</literal> value. See
- <xref linkend="information-functions"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>LAST_INSERT_ID()</literal> function that returns the
+ most recent <literal>AUTO_INCREMENT</literal> value. See
+ <xref linkend="information-functions"/>.
+ </para></listitem>
- <listitem><para>
- <literal>LIKE</literal> is allowed on numeric columns.
- </para></listitem>
+ <listitem><para>
+ <literal>LIKE</literal> is allowed on numeric columns.
+ </para></listitem>
- <listitem><para>
- The <literal>REGEXP</literal> and <literal>NOT REGEXP</literal>
- extended regular expression operators.
- </para></listitem>
+ <listitem><para>
+ The <literal>REGEXP</literal> and <literal>NOT REGEXP</literal>
+ extended regular expression operators.
+ </para></listitem>
- <listitem><para>
- <literal>CONCAT()</literal> or <literal>CHAR()</literal> with one
- argument or more than two arguments. (In MySQL Server, these
- functions can take any number of arguments.)
- </para></listitem>
+ <listitem><para>
+ <literal>CONCAT()</literal> or <literal>CHAR()</literal> with one
+ argument or more than two arguments. (In MySQL Server, these
+ functions can take any number of arguments.)
+ </para></listitem>
- <listitem><para>
- The <literal>BIT_COUNT()</literal>, <literal>CASE</literal>,
- <literal>ELT()</literal>, <literal>FROM_DAYS()</literal>,
- <literal>FORMAT()</literal>, <literal>IF()</literal>,
- <literal>PASSWORD()</literal>, <literal>ENCRYPT()</literal>,
- <literal>MD5()</literal>, <literal>ENCODE()</literal>,
- <literal>DECODE()</literal>, <literal>PERIOD_ADD()</literal>,
- <literal>PERIOD_DIFF()</literal>, <literal>TO_DAYS()</literal>,
- and <literal>WEEKDAY()</literal> functions.
- </para></listitem>
+ <listitem><para>
+ The <literal>BIT_COUNT()</literal>, <literal>CASE</literal>,
+ <literal>ELT()</literal>, <literal>FROM_DAYS()</literal>,
+ <literal>FORMAT()</literal>, <literal>IF()</literal>,
+ <literal>PASSWORD()</literal>, <literal>ENCRYPT()</literal>,
+ <literal>MD5()</literal>, <literal>ENCODE()</literal>,
+ <literal>DECODE()</literal>, <literal>PERIOD_ADD()</literal>,
+ <literal>PERIOD_DIFF()</literal>, <literal>TO_DAYS()</literal>,
+ and <literal>WEEKDAY()</literal> functions.
+ </para></listitem>
- <listitem><para>
- Use of <literal>TRIM()</literal> to trim substrings. Standard SQL
- supports removal of single characters only.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>TRIM()</literal> to trim substrings. Standard SQL
+ supports removal of single characters only.
+ </para></listitem>
- <listitem><para>
- The <literal>GROUP BY</literal> functions
- <literal>STD()</literal>, <literal>BIT_OR()</literal>,
- <literal>BIT_AND()</literal>, <literal>BIT_XOR()</literal>, and
- <literal>GROUP_CONCAT()</literal>. See
- <xref linkend="group-by-functions-and-modifiers"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>GROUP BY</literal> functions
+ <literal>STD()</literal>, <literal>BIT_OR()</literal>,
+ <literal>BIT_AND()</literal>, <literal>BIT_XOR()</literal>, and
+ <literal>GROUP_CONCAT()</literal>. See
+ <xref linkend="group-by-functions-and-modifiers"/>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
</itemizedlist>
--- 1.10/refman/introduction.xml 2005-07-11 15:35:08 -05:00
+++ 1.11/refman/introduction.xml 2005-07-11 15:36:47 -05:00
@@ -160,10 +160,10 @@
<para>
This is the Reference Manual for the MySQL Database System. It
- documents MySQL up to Version ¤t-version;, but is also applicable for
- older versions of the MySQL software (such as 3.23 or 4.0-production)
- because functional changes are indicated with reference to a version
- number.
+ documents MySQL up to Version ¤t-version;, but is also
+ applicable for older versions of the MySQL software (such as 3.23 or
+ 4.0-production) because functional changes are indicated with
+ reference to a version number.
</para>
<para>
@@ -192,12 +192,14 @@
</indexterm>
<para>
- The primary document is a set of
- <ulink url="http://docbook.org/">DocBook</ulink> XML files.
- The HTML version and other formats are produced automatically using,
- among other tools, the
- <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/reference.html">DocBook XSL stylesheets</ulink>.
- <!-- [SH] We might want to add details about creating CHM, PDF, INFO, ... -->
+ The primary document is a set of
+ <ulink url="http://docbook.org/">DocBook</ulink> XML files. The HTML
+ version and other formats are produced automatically using, among
+ other tools, the
+ <ulink url="http://docbook.sourceforge.net/release/xsl/current/doc/reference.html">DocBook
+ XSL stylesheets</ulink>.
+
+<!-- [SH] We might want to add details about creating CHM, PDF, INFO, ... -->
</para>
<para>
@@ -209,17 +211,17 @@
<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
+ consisting of Paul DuBois, Stefan Hinz, Mike Hillyer, and Jon
+ Stephens. For the many other contributors, see
<xref linkend="credits"/>.
</para>
<para>
- The copyright to this manual is owned by the Swedish company
- MySQL AB. MySQL and the MySQL logo are (registered) trademarks of
- MySQL AB. Other trademarks and registered trademarks referred to in
- this manual are the property of their respective owners, and are used
- for identification purposes only.
+ The copyright to this manual is owned by the Swedish company MySQL
+ AB. MySQL and the MySQL logo are (registered) trademarks of MySQL AB.
+ Other trademarks and registered trademarks referred to in this manual
+ are the property of their respective owners, and are used for
+ identification purposes only.
</para>
</section>
@@ -771,10 +773,10 @@
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.
+ 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>
@@ -1264,9 +1266,9 @@
<para>
MySQL 3.22 had a 4GB (4 gigabyte) limit on table size. With the
<literal>MyISAM</literal> storage engine in MySQL 3.23, the maximum
- table size was increased to 65536 terabytes (256 ^ 7 - 1 bytes). With
- this larger allowed table size, the maximum effective table size for
- MySQL databases is usually determined by operating system
+ table size was increased to 65536 terabytes (256 ^ 7 - 1 bytes).
+ With this larger allowed table size, the maximum effective table
+ size for MySQL databases is usually determined by operating system
constraints on file sizes, not by MySQL internal limits.
</para>
@@ -1872,38 +1874,37 @@
forgotten requests from our loyal community of existing users.
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- Most <command>mysqld</command> parameters (startup options) can
- be set without taking down the server. This is a convenient
- feature for database administrators (DBAs). See
- <xref linkend="set-option"/>.
- </para></listitem>
+ <listitem><para>
+ Most <command>mysqld</command> parameters (startup options) can
+ be set without taking down the server. This is a convenient
+ feature for database administrators (DBAs). See
+ <xref linkend="set-option"/>.
+ </para></listitem>
- <listitem><para>
- Multiple-table <literal>DELETE</literal> and
- <literal>UPDATE</literal> statements have been added.
- </para></listitem>
+ <listitem><para>
+ Multiple-table <literal>DELETE</literal> and
+ <literal>UPDATE</literal> statements have been added.
+ </para></listitem>
- <listitem><para>
- On Windows, symbolic link handling at the database level is
- enabled by default. On Unix, the <literal>MyISAM</literal>
- storage engine supports symbolic linking at the table level (and
- not just the database level as before).
- </para></listitem>
+ <listitem><para>
+ On Windows, symbolic link handling at the database level is
+ enabled by default. On Unix, the <literal>MyISAM</literal>
+ storage engine supports symbolic linking at the table level (and
+ not just the database level as before).
+ </para></listitem>
- <listitem><para>
- <literal>SQL_CALC_FOUND_ROWS</literal> and
- <literal>FOUND_ROWS()</literal> are new functions that make it
- possible to find out the number of rows a
- <literal>SELECT</literal> query that includes a
- <literal>LIMIT</literal> clause would have returned without that
- clause.
- </para></listitem>
+ <listitem><para>
+ <literal>SQL_CALC_FOUND_ROWS</literal> and
+ <literal>FOUND_ROWS()</literal> are new functions that make it
+ possible to find out the number of rows a
+ <literal>SELECT</literal> query that includes a
+ <literal>LIMIT</literal> clause would have returned without that
+ clause.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
</itemizedlist>
@@ -1980,10 +1981,11 @@
<para>
MySQL Server 4.0 laid the foundation for new features implemented in
- MySQL 4.1, such as subqueries and Unicode support. These features come
- at the top of the wish list of many of our customers. Well-known for
- its stability, speed, and ease of use, MySQL Server is able to
- fulfill the requirement checklists of very demanding buyers.
+ MySQL 4.1, such as subqueries and Unicode support. These features
+ come at the top of the wish list of many of our customers.
+ Well-known for its stability, speed, and ease of use, MySQL Server
+ is able to fulfill the requirement checklists of very demanding
+ buyers.
</para>
<para>
@@ -3482,45 +3484,45 @@
database directory. This has a few implications:
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><indexterm type="concept">
- <primary>database names</primary>
- <secondary>case-sensitivity</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>case-sensitivity</primary>
- <secondary>of database names</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>table names</primary>
- <secondary>case-sensitivity</secondary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>case-sensitivity</primary>
- <secondary>of table names</secondary>
- </indexterm>
-
- <para>
- Database names and table names are case sensitive in MySQL Server
- on operating systems that have case-sensitive filenames (such as
- most Unix systems). See <xref linkend="name-case-sensitivity"/>.
- </para></listitem>
+ <listitem><indexterm type="concept">
+ <primary>database names</primary>
+ <secondary>case-sensitivity</secondary>
+ </indexterm>
+
+ <indexterm type="concept">
+ <primary>case-sensitivity</primary>
+ <secondary>of database names</secondary>
+ </indexterm>
+
+ <indexterm type="concept">
+ <primary>table names</primary>
+ <secondary>case-sensitivity</secondary>
+ </indexterm>
+
+ <indexterm type="concept">
+ <primary>case-sensitivity</primary>
+ <secondary>of table names</secondary>
+ </indexterm>
+
+ <para>
+ Database names and table names are case sensitive in MySQL Server
+ on operating systems that have case-sensitive filenames (such as
+ most Unix systems). See <xref linkend="name-case-sensitivity"/>.
+ </para></listitem>
- <listitem><para>
- You can use standard system commands to back up, rename, move,
- delete, and copy tables that are managed by the
- <literal>MyISAM</literal> or <literal>ISAM</literal> storage
- engines. For example, to rename a <literal>MyISAM</literal>
- table, rename the <filename>.MYD</filename>,
- <filename>.MYI</filename>, and <filename>.frm</filename> files to
- which the table corresponds.
- </para></listitem>
+ <listitem><para>
+ You can use standard system commands to back up, rename, move,
+ delete, and copy tables that are managed by the
+ <literal>MyISAM</literal> or <literal>ISAM</literal> storage
+ engines. For example, to rename a <literal>MyISAM</literal> table,
+ rename the <filename>.MYD</filename>, <filename>.MYI</filename>,
+ and <filename>.frm</filename> files to which the table
+ corresponds.
+ </para></listitem>
- </itemizedlist>
+ </itemizedlist>
<para>
Database, table, index, column, or alias names may begin with a
@@ -3531,334 +3533,326 @@
General language syntax
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- Strings may be enclosed by either '<literal>"</literal>' or
- '<literal>'</literal>', not just by '<literal>'</literal>'.
- </para></listitem>
+ <listitem><para>
+ Strings may be enclosed by either '<literal>"</literal>' or
+ '<literal>'</literal>', not just by '<literal>'</literal>'.
+ </para></listitem>
- <listitem><para>
- Use of '<literal>\</literal>' as an escape character in strings.
- </para></listitem>
+ <listitem><para>
+ Use of '<literal>\</literal>' as an escape character in strings.
+ </para></listitem>
- <listitem><para>
- In SQL statements, you can access tables from different databases
- with the <replaceable>db_name.tbl_name</replaceable> syntax. Some
- SQL servers provide the same functionality but call this
- <literal>User space</literal>. MySQL Server doesn't support
- tablespaces such as used in statements like this: <literal>CREATE
- TABLE ralph.my_table...IN my_tablespace</literal>.
- </para></listitem>
+ <listitem><para>
+ In SQL statements, you can access tables from different databases
+ with the <replaceable>db_name.tbl_name</replaceable> syntax. Some
+ SQL servers provide the same functionality but call this
+ <literal>User space</literal>. MySQL Server doesn't support
+ tablespaces such as used in statements like this: <literal>CREATE
+ TABLE ralph.my_table...IN my_tablespace</literal>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
SQL statement syntax
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- The <literal>ANALYZE TABLE</literal>, <literal>CHECK
- TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and
- <literal>REPAIR TABLE</literal> statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>ANALYZE TABLE</literal>, <literal>CHECK
+ TABLE</literal>, <literal>OPTIMIZE TABLE</literal>, and
+ <literal>REPAIR TABLE</literal> statements.
+ </para></listitem>
- <listitem><para>
- The <literal>CREATE DATABASE</literal> and <literal>DROP
- DATABASE</literal> statements. See
- <xref linkend="create-database"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>CREATE DATABASE</literal> and <literal>DROP
+ DATABASE</literal> statements. See
+ <xref linkend="create-database"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>DO</literal> statement.
- </para></listitem>
+ <listitem><para>
+ The <literal>DO</literal> statement.
+ </para></listitem>
- <listitem><para>
- <literal>EXPLAIN SELECT</literal> to get a description of how
- tables are joined.
- </para></listitem>
+ <listitem><para>
+ <literal>EXPLAIN SELECT</literal> to get a description of how
+ tables are joined.
+ </para></listitem>
- <listitem><para>
- The <literal>FLUSH</literal> and <literal>RESET</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>FLUSH</literal> and <literal>RESET</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- The <literal>SET</literal> statement. See
- <xref linkend="set-option"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>SET</literal> statement. See
+ <xref linkend="set-option"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>SHOW</literal> statement. See
- <xref linkend="show"/>.
- </para>
+ <listitem><para>
+ The <literal>SHOW</literal> statement. See <xref linkend="show"/>.
+ </para>
- <indexterm type="concept">
- <primary>Oracle compatibility</primary>
- </indexterm>
+ <indexterm type="concept">
+ <primary>Oracle compatibility</primary>
+ </indexterm>
- <indexterm type="concept">
- <primary>compatibility</primary>
- <secondary>with Oracle</secondary>
- </indexterm></listitem>
+ <indexterm type="concept">
+ <primary>compatibility</primary>
+ <secondary>with Oracle</secondary>
+ </indexterm></listitem>
- <listitem><para>
- Use of <literal>LOAD DATA INFILE</literal>. In many cases, this
- syntax is compatible with Oracle's <literal>LOAD DATA
- INFILE</literal>. See <xref linkend="load-data"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>LOAD DATA INFILE</literal>. In many cases, this
+ syntax is compatible with Oracle's <literal>LOAD DATA
+ INFILE</literal>. See <xref linkend="load-data"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>RENAME TABLE</literal>. See
- <xref linkend="rename-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>RENAME TABLE</literal>. See
+ <xref linkend="rename-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>REPLACE</literal> instead of
- <literal>DELETE</literal> + <literal>INSERT</literal>. See
- <xref linkend="replace"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>REPLACE</literal> instead of
+ <literal>DELETE</literal> + <literal>INSERT</literal>. See
+ <xref linkend="replace"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>CHANGE col_name</literal>, <literal>DROP
- col_name</literal>, or <literal>DROP INDEX</literal>,
- <literal>IGNORE</literal> or <literal>RENAME</literal> in an
- <literal>ALTER TABLE</literal> statement. Use of multiple
- <literal>ADD</literal>, <literal>ALTER</literal>,
- <literal>DROP</literal>, or <literal>CHANGE</literal> clauses in
- an <literal>ALTER TABLE</literal> statement. See
- <xref linkend="alter-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>CHANGE col_name</literal>, <literal>DROP
+ col_name</literal>, or <literal>DROP INDEX</literal>,
+ <literal>IGNORE</literal> or <literal>RENAME</literal> in an
+ <literal>ALTER TABLE</literal> statement. Use of multiple
+ <literal>ADD</literal>, <literal>ALTER</literal>,
+ <literal>DROP</literal>, or <literal>CHANGE</literal> clauses in
+ an <literal>ALTER TABLE</literal> statement. See
+ <xref linkend="alter-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of index names, indexes on a prefix of a field, and use of
- <literal>INDEX</literal> or <literal>KEY</literal> in a
- <literal>CREATE TABLE</literal> statement. See
- <xref linkend="create-table"/>.
- </para></listitem>
+ <listitem><para>
+ Use of index names, indexes on a prefix of a field, and use of
+ <literal>INDEX</literal> or <literal>KEY</literal> in a
+ <literal>CREATE TABLE</literal> statement. See
+ <xref linkend="create-table"/>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>TEMPORARY</literal> or <literal>IF NOT
- EXISTS</literal> with <literal>CREATE TABLE</literal>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>TEMPORARY</literal> or <literal>IF NOT
+ EXISTS</literal> with <literal>CREATE TABLE</literal>.
+ </para></listitem>
- <listitem><para>
- Use of <literal>IF EXISTS</literal> with <literal>DROP
- TABLE</literal>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>IF EXISTS</literal> with <literal>DROP
+ TABLE</literal>.
+ </para></listitem>
- <listitem><para>
- You can drop multiple tables with a single <literal>DROP
- TABLE</literal> statement.
- </para></listitem>
+ <listitem><para>
+ You can drop multiple tables with a single <literal>DROP
+ TABLE</literal> statement.
+ </para></listitem>
- <listitem><para>
- The <literal>ORDER BY</literal> and <literal>LIMIT</literal>
- clauses of the <literal>UPDATE</literal> and
- <literal>DELETE</literal> statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>ORDER BY</literal> and <literal>LIMIT</literal>
+ clauses of the <literal>UPDATE</literal> and
+ <literal>DELETE</literal> statements.
+ </para></listitem>
- <listitem><para>
- <literal>INSERT INTO ... SET col_name = ...</literal> syntax.
- </para></listitem>
+ <listitem><para>
+ <literal>INSERT INTO ... SET col_name = ...</literal> syntax.
+ </para></listitem>
- <listitem><para>
- The <literal>DELAYED</literal> clause of the
- <literal>INSERT</literal> and <literal>REPLACE</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>DELAYED</literal> clause of the
+ <literal>INSERT</literal> and <literal>REPLACE</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- The <literal>LOW_PRIORITY</literal> clause of the
- <literal>INSERT</literal>, <literal>REPLACE</literal>,
- <literal>DELETE</literal>, and <literal>UPDATE</literal>
- statements.
- </para></listitem>
+ <listitem><para>
+ The <literal>LOW_PRIORITY</literal> clause of the
+ <literal>INSERT</literal>, <literal>REPLACE</literal>,
+ <literal>DELETE</literal>, and <literal>UPDATE</literal>
+ statements.
+ </para></listitem>
- <listitem><para>
- Use of <literal>INTO OUTFILE</literal> and
- <literal>STRAIGHT_JOIN</literal> in a <literal>SELECT</literal>
- statement. See <xref linkend="select"/>.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>INTO OUTFILE</literal> and
+ <literal>STRAIGHT_JOIN</literal> in a <literal>SELECT</literal>
+ statement. See <xref linkend="select"/>.
+ </para></listitem>
- <listitem><para>
- The <literal>SQL_SMALL_RESULT</literal> option in a
- <literal>SELECT</literal> statement.
- </para></listitem>
+ <listitem><para>
+ The <literal>SQL_SMALL_RESULT</literal> option in a
+ <literal>SELECT</literal> statement.
+ </para></listitem>
- <listitem><para>
- You don't need to name all selected columns in the <literal>GROUP
- BY</literal> part. This gives better performance for some very
- specific, but quite normal queries. See
- <xref linkend="group-by-functions-and-modifiers"/>.
- </para></listitem>
+ <listitem><para>
+ You don't need to name all selected columns in the <literal>GROUP
+ BY</literal> part. This gives better performance for some very
+ specific, but quite normal queries. See
+ <xref linkend="group-by-functions-and-modifiers"/>.
+ </para></listitem>
- <listitem><para>
- You can specify <literal>ASC</literal> and
- <literal>DESC</literal> with <literal>GROUP BY</literal>.
- </para></listitem>
+ <listitem><para>
+ You can specify <literal>ASC</literal> and <literal>DESC</literal>
+ with <literal>GROUP BY</literal>.
+ </para></listitem>
- <listitem><para>
- The ability to set variables in a statement with the
- <literal>:=</literal> assignment operator:
+ <listitem><para>
+ The ability to set variables in a statement with the
+ <literal>:=</literal> assignment operator:
<programlisting>
mysql> SELECT @a:=SUM(total),@b=COUNT(*),@a/@b AS avg
-> FROM test_table;
mysql> SELECT @t1:=(@t2:=1)+@t3:=4,@t1,@t2,@t3;
</programlisting>
- </para></listitem>
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
Column types
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- The column types <literal>MEDIUMINT</literal>,
- <literal>SET</literal>, <literal>ENUM</literal>, and the
- different <literal>BLOB</literal> and <literal>TEXT</literal>
- types.
- </para></listitem>
+ <listitem><para>
+ The column types <literal>MEDIUMINT</literal>,
+ <literal>SET</literal>, <literal>ENUM</literal>, and the different
+ <literal>BLOB</literal> and <literal>TEXT</literal> types.
+ </para></listitem>
- <listitem><para>
- The column attributes <literal>AUTO_INCREMENT</literal>,
- <literal>BINARY</literal>, <literal>NULL</literal>,
- <literal>UNSIGNED</literal>, and <literal>ZEROFILL</literal>.
- </para></listitem>
+ <listitem><para>
+ The column attributes <literal>AUTO_INCREMENT</literal>,
+ <literal>BINARY</literal>, <literal>NULL</literal>,
+ <literal>UNSIGNED</literal>, and <literal>ZEROFILL</literal>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
<listitem><para>
Functions and operators
</para>
- <itemizedlist>
+ <itemizedlist>
- <listitem><para>
- To make it easier for users who come from other SQL environments,
- MySQL Server supports aliases for many functions. For example,
- all string functions support both standard SQL syntax and ODBC
- syntax.
- </para></listitem>
+ <listitem><para>
+ To make it easier for users who come from other SQL environments,
+ MySQL Server supports aliases for many functions. For example, all
+ string functions support both standard SQL syntax and ODBC syntax.
+ </para></listitem>
- <listitem><para>
- MySQL Server understands the <literal>||</literal> and
- <literal>&&</literal> operators to mean logical OR and
- AND, as in the C programming language. In MySQL Server,
- <literal>||</literal> and <literal>OR</literal> are synonyms, as
- are <literal>&&</literal> and <literal>AND</literal>.
- Because of this nice syntax, MySQL Server doesn't support the
- standard SQL <literal>||</literal> operator for string
- concatenation; use <literal>CONCAT()</literal> instead. Because
- <literal>CONCAT()</literal> takes any number of arguments, it's
- easy to convert use of the <literal>||</literal> operator to
- MySQL Server.
- </para></listitem>
+ <listitem><para>
+ MySQL Server understands the <literal>||</literal> and
+ <literal>&&</literal> operators to mean logical OR and
+ AND, as in the C programming language. In MySQL Server,
+ <literal>||</literal> and <literal>OR</literal> are synonyms, as
+ are <literal>&&</literal> and <literal>AND</literal>.
+ Because of this nice syntax, MySQL Server doesn't support the
+ standard SQL <literal>||</literal> operator for string
+ concatenation; use <literal>CONCAT()</literal> instead. Because
+ <literal>CONCAT()</literal> takes any number of arguments, it's
+ easy to convert use of the <literal>||</literal> operator to MySQL
+ Server.
+ </para></listitem>
- <listitem><para>
- Use of <literal>COUNT(DISTINCT list)</literal> where
- <literal>list</literal> has more than one element.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>COUNT(DISTINCT list)</literal> where
+ <literal>list</literal> has more than one element.
+ </para></listitem>
- <listitem><para>
- All string comparisons are case-insensitive by default, with sort
- ordering determined by the current character set (ISO-8859-1
- Latin1 by default). If you don't like this, you should declare
- your columns with the <literal>BINARY</literal> attribute or use
- the <literal>BINARY</literal> cast, which causes comparisons to
- be done using the underlying character code values rather then a
- lexical ordering.
- </para>
+ <listitem><para>
+ All string comparisons are case-insensitive by default, with sort
+ ordering determined by the current character set (ISO-8859-1
+ Latin1 by default). If you don't like this, you should declare
+ your columns with the <literal>BINARY</literal> attribute or use
+ the <literal>BINARY</literal> cast, which causes comparisons to be
+ done using the underlying character code values rather then a
+ lexical ordering.
+ </para>
- <indexterm type="concept">
- <primary>PostgreSQL compatibility</primary>
- </indexterm>
-
- <indexterm type="concept">
- <primary>compatibility</primary>
- <secondary>with PostgreSQL</secondary>
- </indexterm></listitem>
-
- <listitem><para>
- The <literal>%</literal> operator is a synonym for
- <literal>MOD()</literal>. That is, <literal>N % M</literal> is
- equivalent to <literal>MOD(N,M)</literal>. <literal>%</literal>
- is supported for C programmers and for compatibility with
- PostgreSQL.
- </para></listitem>
+ <indexterm type="concept">
+ <primary>PostgreSQL compatibility</primary>
+ </indexterm>
- <listitem><para>
- The <literal>=</literal>, <literal><></literal>,
- <literal><=</literal> ,<literal><</literal>,
- <literal>>=</literal>,<literal>></literal>,
- <literal><<</literal>, <literal>>></literal>,
- <literal><=></literal>, <literal>AND</literal>,
- <literal>OR</literal>, or <literal>LIKE</literal> operators may
- be used in column comparisons to the left of the
- <literal>FROM</literal> in <literal>SELECT</literal> statements.
- For example:
- </para>
+ <indexterm type="concept">
+ <primary>compatibility</primary>
+ <secondary>with PostgreSQL</secondary>
+ </indexterm></listitem>
+
+ <listitem><para>
+ The <literal>%</literal> operator is a synonym for
+ <literal>MOD()</literal>. That is, <literal>N % M</literal> is
+ equivalent to <literal>MOD(N,M)</literal>. <literal>%</literal> is
+ supported for C programmers and for compatibility with PostgreSQL.
+ </para></listitem>
+
+ <listitem><para>
+ The <literal>=</literal>, <literal><></literal>,
+ <literal><=</literal> ,<literal><</literal>,
+ <literal>>=</literal>,<literal>></literal>,
+ <literal><<</literal>, <literal>>></literal>,
+ <literal><=></literal>, <literal>AND</literal>,
+ <literal>OR</literal>, or <literal>LIKE</literal> operators may be
+ used in column comparisons to the left of the
+ <literal>FROM</literal> in <literal>SELECT</literal> statements.
+ For example:
+ </para>
<programlisting>
mysql> SELECT col1=1 AND col2=2 FROM <replaceable>tbl_name</replaceable>;
</programlisting></listitem>
- <listitem><para>
- The <literal>LAST_INSERT_ID()</literal> function that returns the
- most recent <literal>AUTO_INCREMENT</literal> value. See
- <xref linkend="information-functions"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>LAST_INSERT_ID()</literal> function that returns the
+ most recent <literal>AUTO_INCREMENT</literal> value. See
+ <xref linkend="information-functions"/>.
+ </para></listitem>
- <listitem><para>
- <literal>LIKE</literal> is allowed on numeric columns.
- </para></listitem>
+ <listitem><para>
+ <literal>LIKE</literal> is allowed on numeric columns.
+ </para></listitem>
- <listitem><para>
- The <literal>REGEXP</literal> and <literal>NOT REGEXP</literal>
- extended regular expression operators.
- </para></listitem>
+ <listitem><para>
+ The <literal>REGEXP</literal> and <literal>NOT REGEXP</literal>
+ extended regular expression operators.
+ </para></listitem>
- <listitem><para>
- <literal>CONCAT()</literal> or <literal>CHAR()</literal> with one
- argument or more than two arguments. (In MySQL Server, these
- functions can take any number of arguments.)
- </para></listitem>
+ <listitem><para>
+ <literal>CONCAT()</literal> or <literal>CHAR()</literal> with one
+ argument or more than two arguments. (In MySQL Server, these
+ functions can take any number of arguments.)
+ </para></listitem>
- <listitem><para>
- The <literal>BIT_COUNT()</literal>, <literal>CASE</literal>,
- <literal>ELT()</literal>, <literal>FROM_DAYS()</literal>,
- <literal>FORMAT()</literal>, <literal>IF()</literal>,
- <literal>PASSWORD()</literal>, <literal>ENCRYPT()</literal>,
- <literal>MD5()</literal>, <literal>ENCODE()</literal>,
- <literal>DECODE()</literal>, <literal>PERIOD_ADD()</literal>,
- <literal>PERIOD_DIFF()</literal>, <literal>TO_DAYS()</literal>,
- and <literal>WEEKDAY()</literal> functions.
- </para></listitem>
+ <listitem><para>
+ The <literal>BIT_COUNT()</literal>, <literal>CASE</literal>,
+ <literal>ELT()</literal>, <literal>FROM_DAYS()</literal>,
+ <literal>FORMAT()</literal>, <literal>IF()</literal>,
+ <literal>PASSWORD()</literal>, <literal>ENCRYPT()</literal>,
+ <literal>MD5()</literal>, <literal>ENCODE()</literal>,
+ <literal>DECODE()</literal>, <literal>PERIOD_ADD()</literal>,
+ <literal>PERIOD_DIFF()</literal>, <literal>TO_DAYS()</literal>,
+ and <literal>WEEKDAY()</literal> functions.
+ </para></listitem>
- <listitem><para>
- Use of <literal>TRIM()</literal> to trim substrings. Standard SQL
- supports removal of single characters only.
- </para></listitem>
+ <listitem><para>
+ Use of <literal>TRIM()</literal> to trim substrings. Standard SQL
+ supports removal of single characters only.
+ </para></listitem>
- <listitem><para>
- The <literal>GROUP BY</literal> functions
- <literal>STD()</literal>, <literal>BIT_OR()</literal>,
- <literal>BIT_AND()</literal>, <literal>BIT_XOR()</literal>, and
- <literal>GROUP_CONCAT()</literal>. See
- <xref linkend="group-by-functions-and-modifiers"/>.
- </para></listitem>
+ <listitem><para>
+ The <literal>GROUP BY</literal> functions
+ <literal>STD()</literal>, <literal>BIT_OR()</literal>,
+ <literal>BIT_AND()</literal>, <literal>BIT_XOR()</literal>, and
+ <literal>GROUP_CONCAT()</literal>. See
+ <xref linkend="group-by-functions-and-modifiers"/>.
+ </para></listitem>
- </itemizedlist>
- </listitem>
+ </itemizedlist></listitem>
</itemizedlist>
| Thread |
|---|
| • bk commit - mysqldoc@docsrva tree (paul:1.2992) | paul | 11 Jul |
