Author: jstephens
Date: 2007-01-10 09:34:07 +0100 (Wed, 10 Jan 2007)
New Revision: 4430
Log:
Merged 4-1-features section into mysql-4-1-nutshell (request from Bryan)
Modified:
trunk/refman-4.1/introduction.xml
trunk/refman-4.1/renamed-nodes.txt
Modified: trunk/refman-4.1/introduction.xml
===================================================================
--- trunk/refman-4.1/introduction.xml 2007-01-10 07:54:15 UTC (rev 4429)
+++ trunk/refman-4.1/introduction.xml 2007-01-10 08:34:07 UTC (rev 4430)
Changed blocks: 1, Lines Added: 232, Lines Deleted: 243; 19952 bytes
@@ -659,295 +659,284 @@
available. See <xref linkend="installing-source-tree"/>.
</para>
- <section id="nutshell-4-1-features">
+ <para>
+ The following features are implemented in MySQL 4.1. Features
+ that are available in MySQL 5.0 are described in
+ <xref linkend="mysql-5-0-nutshell"/>.
+ </para>
- <title>Features Available in MySQL 4.1</title>
+ <itemizedlist>
- <para>
- This section lists features implemented in MySQL 4.1. Features
- that are available in MySQL 5.0 are described in
- <xref linkend="mysql-5-0-nutshell"/>.
- </para>
+ <listitem>
+ <para>
+ <emphasis role="bold">Support for subqueries and derived
+ tables</emphasis>:
+ </para>
- <itemizedlist>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Support for subqueries and derived
- tables</emphasis>:
- </para>
+ <listitem>
+ <para>
+ A <quote>subquery</quote> is a <literal>SELECT</literal>
+ statement nested within another statement. A
+ <quote>derived table</quote> (an unnamed view) is a
+ subquery in the <literal>FROM</literal> clause of
+ another statement. See <xref linkend="subqueries"/>.
+ </para>
+ </listitem>
- <itemizedlist>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- A <quote>subquery</quote> is a
- <literal>SELECT</literal> statement nested within
- another statement. A <quote>derived table</quote> (an
- unnamed view) is a subquery in the
- <literal>FROM</literal> clause of another statement.
- See <xref linkend="subqueries"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Speed enhancements</emphasis>:
+ </para>
- </itemizedlist>
- </listitem>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Speed enhancements</emphasis>:
- </para>
+ <listitem>
+ <para>
+ Faster binary client/server protocol with support for
+ prepared statements and parameter binding. See
+ <xref linkend="c-api-prepared-statements"/>.
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ <literal>BTREE</literal> indexing is supported for
+ <literal>HEAP</literal> tables, significantly improving
+ response time for non-exact searches.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Faster binary client/server protocol with support for
- prepared statements and parameter binding. See
- <xref linkend="c-api-prepared-statements"/>.
- </para>
- </listitem>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- <literal>BTREE</literal> indexing is supported for
- <literal>HEAP</literal> tables, significantly
- improving response time for non-exact searches.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Added functionality</emphasis>:
+ </para>
- </itemizedlist>
- </listitem>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Added functionality</emphasis>:
- </para>
+ <listitem>
+ <para>
+ <literal>CREATE TABLE
+ <replaceable>tbl_name2</replaceable> LIKE
+ <replaceable>tbl_name1</replaceable></literal> allows
+ you to create, with a single statement, a new table with
+ a structure exactly like that of an existing table.
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ The <literal>MyISAM</literal> storage engine added
+ support for OpenGIS spatial types for storing
+ geographical data. See
+ <xref linkend="spatial-extensions"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <literal>CREATE TABLE
- <replaceable>tbl_name2</replaceable> LIKE
- <replaceable>tbl_name1</replaceable></literal> allows
- you to create, with a single statement, a new table
- with a structure exactly like that of an existing
- table.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Support was added for replication over SSL connections.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The <literal>MyISAM</literal> storage engine added
- support for OpenGIS spatial types for storing
- geographical data. See
- <xref linkend="spatial-extensions"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Support for a number of additional storage engines was
+ implemented in the MySQL 4.1 release series:
+ </para>
- <listitem>
- <para>
- Support was added for replication over SSL
- connections.
- </para>
- </listitem>
+ <itemizedlist>
- <listitem>
- <para>
- Support for a number of additional storage engines was
- implemented in the MySQL 4.1 release series:
- </para>
+ <listitem>
+ <para>
+ The <literal>EXAMPLE</literal> storage engine is a
+ <quote>stub</quote> engine that serves as an example
+ in the MySQL source code for writing new storage
+ engines, and is primarily of interest to developers.
+ See <xref linkend="example-storage-engine"/>.
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ <literal>NDB Cluster</literal> is the storage engine
+ used by MySQL Cluster to implement tables that are
+ partitioned over many computers. See
+ <xref linkend="mysql-cluster"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The <literal>EXAMPLE</literal> storage engine is a
- <quote>stub</quote> engine that serves as an
- example in the MySQL source code for writing new
- storage engines, and is primarily of interest to
- developers. See
- <xref linkend="example-storage-engine"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The <literal>ARCHIVE</literal> storage engine is
+ used for storing large amounts of data without
+ indexes in a very small footprint. See
+ <xref linkend="archive-storage-engine"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- <literal>NDB Cluster</literal> is the storage
- engine used by MySQL Cluster to implement tables
- that are partitioned over many computers. See
- <xref linkend="mysql-cluster"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The <literal>CSV</literal> storage engine stores
+ data in text files using comma-separated values
+ format. See <xref linkend="csv-storage-engine"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The <literal>ARCHIVE</literal> storage engine is
- used for storing large amounts of data without
- indexes in a very small footprint. See
- <xref linkend="archive-storage-engine"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The <literal>BLACKHOLE</literal> storage engine
+ accepts but does not store data, and always returns
+ an empty result set. It is for use primarily in
+ replication. See
+ <xref linkend="blackhole-storage-engine"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The <literal>CSV</literal> storage engine stores
- data in text files using comma-separated values
- format. See <xref linkend="csv-storage-engine"/>.
- </para>
- </listitem>
+ </itemizedlist>
- <listitem>
- <para>
- The <literal>BLACKHOLE</literal> storage engine
- accepts but does not store data, and always
- returns an empty result set. It is for use
- primarily in replication. See
- <xref linkend="blackhole-storage-engine"/>.
- </para>
- </listitem>
+ <para>
+ <emphasis role="bold">Note</emphasis>: These engine were
+ implemented at different points in the development of
+ MySQL 4.1. Please see the indicated sections for
+ particulars in each case.
+ </para>
+ </listitem>
- </itemizedlist>
+ </itemizedlist>
+ </listitem>
- <para>
- <emphasis role="bold">Note</emphasis>: These engine
- were implemented at different points in the
- development of MySQL 4.1. Please see the indicated
- sections for particulars in each case.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Standards compliance, portability, and
+ migration</emphasis>:
+ </para>
- </itemizedlist>
- </listitem>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Standards compliance, portability,
- and migration</emphasis>:
- </para>
+ <listitem>
+ <para>
+ The enhanced client/server protocol available beginning
+ with MySQL 4.1.1 provides the ability to pass multiple
+ warnings to the client, rather than only a single
+ result, making it much easier to track problems that
+ occur in operations such as bulk data loading.
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ <literal>SHOW WARNINGS</literal> shows warnings for the
+ last command. See <xref linkend="show-warnings"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The enhanced client/server protocol available
- beginning with MySQL 4.1.1 provides the ability to
- pass multiple warnings to the client, rather than only
- a single result, making it much easier to track
- problems that occur in operations such as bulk data
- loading.
- </para>
- </listitem>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- <literal>SHOW WARNINGS</literal> shows warnings for
- the last command. See <xref linkend="show-warnings"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Internationalization and
+ Localization</emphasis>:
+ </para>
- </itemizedlist>
- </listitem>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Internationalization and
- Localization</emphasis>:
- </para>
+ <listitem>
+ <para>
+ To support applications that require the use of local
+ languages, the MySQL software added extensive Unicode
+ support through the <literal>utf8</literal> and
+ <literal>ucs2</literal> character sets.
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ Definition of character sets by column, table, and
+ database. This allows for a high degree of flexibility
+ in application design, particularly for multi-language
+ Web sites. See <xref linkend="charset"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- To support applications that require the use of local
- languages, the MySQL software added extensive Unicode
- support through the <literal>utf8</literal> and
- <literal>ucs2</literal> character sets.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ Per-connection time zones support, allowing individual
+ clients to select their own time zones when necessary.
+ </para>
+ </listitem>
- <listitem>
- <para>
- Definition of character sets by column, table, and
- database. This allows for a high degree of flexibility
- in application design, particularly for multi-language
- Web sites. See <xref linkend="charset"/>.
- </para>
- </listitem>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- Per-connection time zones support, allowing individual
- clients to select their own time zones when necessary.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Usability enhancements</emphasis>:
+ </para>
- </itemizedlist>
- </listitem>
+ <itemizedlist>
- <listitem>
- <para>
- <emphasis role="bold">Usability enhancements</emphasis>:
- </para>
+ <listitem>
+ <para>
+ The addition of a server-based <literal>HELP</literal>
+ command that can be used to get help information for SQL
+ statements. This information is always applicable to the
+ particular server version being used. Because this
+ information is available by issuing an SQL statement,
+ any client can access it. For example, the
+ <literal>help</literal> command of the
+ <command>mysql</command> command-line client has been
+ modified to have this capability.
+ </para>
+ </listitem>
- <itemizedlist>
+ <listitem>
+ <para>
+ The improved client/server protocol allows multiple
+ statements to be issued with a single call, and for
+ returning multiple result sets. See
+ <xref linkend="c-api-multiple-queries"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The addition of a server-based <literal>HELP</literal>
- command that can be used to get help information for
- SQL statements. This information is always applicable
- to the particular server version being used. Because
- this information is available by issuing an SQL
- statement, any client can access it. For example, the
- <literal>help</literal> command of the
- <command>mysql</command> command-line client has been
- modified to have this capability.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The syntax <literal>INSERT ... ON DUPLICATE KEY UPDATE
+ ...</literal> was implemented. This allows you to update
+ an existing row if the insert would have caused a
+ duplicate value for a primary or unique index. See
+ <xref linkend="insert"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The improved client/server protocol allows multiple
- statements to be issued with a single call, and for
- returning multiple result sets. See
- <xref linkend="c-api-multiple-queries"/>.
- </para>
- </listitem>
+ <listitem>
+ <para>
+ The aggregate function
+ <literal>GROUP_CONCAT()</literal>, added the capability
+ to concatenate column values from grouped rows into a
+ single result string. See
+ <xref linkend="group-by-functions-and-modifiers"/>.
+ </para>
+ </listitem>
- <listitem>
- <para>
- The syntax <literal>INSERT ... ON DUPLICATE KEY UPDATE
- ...</literal> was implemented. This allows you to
- update an existing row if the insert would have caused
- a duplicate value for a primary or unique index. See
- <xref linkend="insert"/>.
- </para>
- </listitem>
+ </itemizedlist>
+ </listitem>
- <listitem>
- <para>
- The aggregate function
- <literal>GROUP_CONCAT()</literal>, added the
- capability to concatenate column values from grouped
- rows into a single result string. See
- <xref linkend="group-by-functions-and-modifiers"/>.
- </para>
- </listitem>
+ </itemizedlist>
- </itemizedlist>
- </listitem>
+ <para>
+ The News section of this manual includes a more in-depth list of
+ MySQL 4.1 features. See <xref linkend="news-4-1-x"/>.
+ </para>
- </itemizedlist>
-
- <para>
- The News section of this manual includes a more in-depth list
- of MySQL 4.1 features. See <xref linkend="news-4-1-x"/>.
- </para>
-
- </section>
-
</section>
<section id="mysql-5-0-nutshell">
Modified: trunk/refman-4.1/renamed-nodes.txt
===================================================================
--- trunk/refman-4.1/renamed-nodes.txt 2007-01-10 07:54:15 UTC (rev 4429)
+++ trunk/refman-4.1/renamed-nodes.txt 2007-01-10 08:34:07 UTC (rev 4430)
Changed blocks: 1, Lines Added: 1, Lines Deleted: 0; 482 bytes
@@ -297,5 +297,6 @@
system system-optimization
nutshell-4-0-features mysql-4-0-nutshell
nutshell-embedded-mysql mysql-4-0-nutshell
+nutshell-4-1-features mysql-4-1-nutshell
table-size full-table
year-2000-compliance y2k-issues
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r4430 - trunk/refman-4.1 | jon | 10 Jan |
