| List: | Internals | « Previous MessageNext Message » | |
| From: | jstephens | Date: | October 19 2005 2:53pm |
| Subject: | svn commit - mysqldoc@docsrva: r97 - in trunk: refman-5.0 refman-5.1 refman-common | ||
| View as plain text | |||
Author: jstephens Date: 2005-10-19 14:53:47 +0200 (Wed, 19 Oct 2005) New Revision: 97 Log: refman-common/titles.en.ent - Added title for new 5.1 Nutshell section refman-5.0/introduction.xml - Cut 4.0 and 4.1 Nutshell sections refman-5.1/introduction.xml - Cut 4.0 and 4.1 Nutshell sections; added placeholder 5.1 Nutshell section refman-5.0/renamed-nodes.txt - Added redirects for 4.1 sections cut from 5.0 Manual Modified: trunk/refman-5.0/introduction.xml trunk/refman-5.0/renamed-nodes.txt trunk/refman-5.1/introduction.xml trunk/refman-common/titles.en.ent Modified: trunk/refman-5.0/introduction.xml =================================================================== --- trunk/refman-5.0/introduction.xml 2005-10-19 10:22:27 UTC (rev 96) +++ trunk/refman-5.0/introduction.xml 2005-10-19 12:53:47 UTC (rev 97) @@ -388,613 +388,7 @@ </tbody> </tgroup> </informaltable> - - <section id="mysql-4-0-nutshell"> - - <title id="title-mysql-4-0-nutshell">&title-mysql-4-0-nutshell;</title> - - <para> - MySQL 4.0 is available for download at - <ulink url="http://dev.mysql.com/"/> and from our mirrors. MySQL - 4.0 has been tested by a large number of users and is in - production use at many large sites. - </para> - - <section id="nutshell-4-0-features"> - - <title id="title-nutshell-4-0-features">&title-nutshell-4-0-features;</title> - - <itemizedlist> - - <listitem> - <para> - Speed enhancements - </para> - - <itemizedlist> - - <listitem> - <para> - MySQL 4.0 implemented a query cache that can give a - major speed boost to applications with repetitive - queries. See <xref linkend="query-cache"/>. - </para> - </listitem> - - <listitem> - <para> - Version 4.0 further increased the speed of MySQL - Server in a number of areas, such as bulk - <literal>INSERT</literal> statements, searching on - packed indexes, full-text searching (using - <literal>FULLTEXT</literal> indexes), and - <literal>COUNT(DISTINCT)</literal>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - Introduction of Embedded MySQL Server - </para> - - <itemizedlist> - - <listitem> - <para> - The Embedded Server library added in this release can - easily be used to create standalone and embedded - applications. The embedded server provides an - alternative to using MySQL in a client/server - environment. See - <xref linkend="nutshell-embedded-mysql"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <literal>InnoDB</literal> storage engine as standard - </para> - - <itemizedlist> - - <listitem> - <para> - The <literal>InnoDB</literal> storage engine began to - be offered as a standard feature of the MySQL server. - This provided full support for ACID transactions, - foreign keys with cascading <literal>UPDATE</literal> - and <literal>DELETE</literal>, and row-level locking - as standard features. See <xref linkend="innodb"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - New functionality - </para> - - <itemizedlist> - - <listitem> - <para> - The enhanced <literal>FULLTEXT</literal> search - capabilities of MySQL Server 4.0 enabled - <literal>FULLTEXT</literal> indexing of large text - masses with both binary and natural-language searching - logic. It became possible to customize minimal word - length and define your own stop word lists in most - human languages, enabling a broader class of - applications to be built with MySQL Server. See - <xref linkend="fulltext-search"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - Standards compliance, portability, and migration - </para> - - <itemizedlist> - - <listitem> - <para> - MySQL Server added support for the - <literal>UNION</literal> statement, a standard SQL - feature. - </para> - </listitem> - - <listitem> - <para> - Starting with version 4.0, MySQL runs natively on - Novell NetWare 6.0 and higher. See - <xref linkend="netware-installation"/>. - </para> - </listitem> - - <listitem> - <para> - Features to simplify migration from other database - systems to MySQL Server include <literal>TRUNCATE - TABLE</literal> (as in Oracle) - - <remark role="note"> - Commented out IDENTITY until someone explains what - it means... - </remark> - - - - <remark> - and IDENTITY as a synonym for automatically - incremented keys (as in Sybase) - </remark> - - . - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - Internationalization - </para> - - <itemizedlist> - - <listitem> - <para> - German-speaking users should note that MySQL 4.0 added - support for a new character set, - <literal>latin1_de</literal>, which ensures that words - with umlauts are sorted in the same order as in German - telephone books. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Usability enhancements</emphasis> - </para> - - <itemizedlist> - - <listitem> - <para> - As of Version 4.0, most <command>mysqld</command> - parameters (startup options) can be set without taking - down the server. This is a convenient feature for - database administrators. See - <xref linkend="set-option"/>. - </para> - </listitem> - - <listitem> - <para> - Multiple-table <literal>DELETE</literal> and - <literal>UPDATE</literal> statements were added. - </para> - </listitem> - - <listitem> - <para> - On Windows, symbolic link handling at the database - level was enabled by default. On Unix, the - <literal>MyISAM</literal> storage engine added support - for symbolic linking at the table level (and not just - the database level as before). - </para> - </listitem> - - <listitem> - <para> - The addition of the - <literal>SQL_CALC_FOUND_ROWS</literal> and - <literal>FOUND_ROWS()</literal> functions made 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> - - <para> - For a more comprehensive list of MySQL 4.0 features, see the - &title-refman-4-1;, available at the MySQL AB website, which - covers MySQL 4.1 and previous versions of the MySQL server - software. - </para> - - </section> - - <section id="nutshell-embedded-mysql"> - - <title id="title-nutshell-embedded-mysql">&title-nutshell-embedded-mysql;</title> - - <para> - The <literal>libmysqld</literal> embedded server library made - MySQL Server suitable for a wider range of applications. 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 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> - The embedded MySQL library uses the same interface as the - normal client library. See <xref linkend="libmysqld"/>. - Embedded MySQL is available under the same dual-licensing - model as the MySQL Server; see - <ulink url="http://www.mysql.com/company/legal/licensing/"/> - for more information. - </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> - - <section id="mysql-4-1-nutshell"> - - <title id="title-mysql-4-1-nutshell">&title-mysql-4-1-nutshell;</title> - - <para> - MySQL Server 4.0 laid the foundation for new features - implemented in MySQL 4.1, such as subqueries and Unicode - support, which were desired by many of our customers. - </para> - - <para> - MySQL Server 4.1 is currently in production status, and binaries - are available for download at - <ulink url="http://dev.mysql.com/downloads/mysql/4.1.html"/>. - All binary releases pass our extensive test suite without any - errors on the platforms on which we test. See the - &title-refman-4-1;, available at the MySQL AB website for more - specific information. - </para> - - <para> - For those wishing to use the most recent development source for - MySQL 4.1, we also make our BitKeeper repositories publicly - available. See <xref linkend="installing-source-tree"/>. - </para> - - <section id="nutshell-4-1-features"> - - <title id="title-nutshell-4-1-features">&title-nutshell-4-1-features;</title> - - <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> - - <itemizedlist> - - <listitem> - <para> - <emphasis role="bold">Support for subqueries and derived - tables</emphasis>: - </para> - - <itemizedlist> - - <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> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Speed enhancements</emphasis>: - </para> - - <itemizedlist> - - <listitem> - <para> - Faster binary client/server protocol with support for - prepared statements and parameter binding. See - <xref linkend="c-api-prepared-statements"/>. - </para> - </listitem> - - <listitem> - <para> - <literal>BTREE</literal> indexing is supported for - <literal>HEAP</literal> tables, significantly - improving response time for non-exact searches. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Added functionality</emphasis>: - </para> - - <itemizedlist> - - <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> - The <literal>MyISAM</literal> storage engine added - support for OpenGIS spatial types for storing - geographical data. See - <xref linkend="spatial-extensions-in-mysql"/>. - </para> - </listitem> - - <listitem> - <para> - Support was added for replication over SSL - connections. - </para> - </listitem> - - <listitem> - <para> - Support for a number of additional storage engines was - implemented in the MySQL 4.1 release series: - - <itemizedlist> - - <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> - <literal>NDB Cluster</literal> is the storage - engine used by MySQL Cluster to implement tables - that are partitioned over many computers. See - <xref linkend="ndbcluster"/>. - </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>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>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> - - </itemizedlist> - - <emphasis role="bold">Note</emphasis>: These engines - 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> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Standards compliance, portability, - and migration</emphasis>: - </para> - - <itemizedlist> - - <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> - - <listitem> - <para> - <literal>SHOW WARNINGS</literal> shows warnings for - the last command. See <xref linkend="show-warnings"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Internationalization and - Localization</emphasis>: - </para> - - <itemizedlist> - - <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> - 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> - Per-connection time zones support, allowing individual - clients to select their own time zones when necessary. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Usability enhancements</emphasis>: - </para> - - <itemizedlist> - - <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 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 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 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> - </listitem> - - </itemizedlist> - - <para> - For a more comprehensive list of MySQL 4.1 features, see the - &title-refman-4-1;, available at the MySQL AB website. - </para> - - </section> - - </section> - + <section id="mysql-5-0-nutshell"> <title id="title-mysql-5-0-nutshell">&title-mysql-5-0-nutshell;</title> @@ -1087,32 +481,16 @@ and <xref linkend="ansi-diff-triggers"/>. </para> </listitem> - + <listitem> <para> <emphasis role="bold"><literal>VARCHAR</literal> Data - Type</emphasis>: The maximum effective length of a + Type</emphasis>: The maximum effective length of a <literal>VARCHAR</literal> column was increased to 65,532 bytes, and stripping of trailing whitespace was eliminated. See <xref linkend="string-types"/>. </para> - - <para> - Note that the new <literal>VARCHAR</literal> type can be - handled more quickly than in previous MySQL versions since - whitespace removal is no longer performed. - </para> </listitem> - - <listitem> - <para> - <emphasis role="bold"><literal>BIT</literal> Data - Type</emphasis>: This is a true Boolean type which can - store true/false values more compactly than workarounds such - as <literal>CHAR(0)</literal>. See <xref - linkend="numeric-type-overview"/>. - </para> - </listitem> <listitem> <para> @@ -1129,208 +507,12 @@ <xref linkend="xa"/>. </para> </listitem> - - <listitem> - <para> - <emphasis role="bold">Performance enhancements</emphasis>: - A number of improvements were made in MySQL 5.0 to improve - the speed of certain types of queries and in the handling of - certain types. These include: - </para> - - <itemizedlist> - <listitem> - <para> - Improved handling of multi-table joins even where - there are no good keys to use. - </para> - </listitem> - - <listitem> - <para> - Better optimization of <literal>OR</literal> over - different keys, such as <literal>... WHERE key1=5 OR - key2=6</literal>. (Previously, <literal>OR</literal> - was optimized only where both relations involved the - same key.) This also applies to other one-to-one - comparison operators (<literal>></literal>, - <literal><</literal>, and so on), as well as - <literal>=</literal>. - </para> - </listitem> - - <listitem> - <para> - New equality detector that finds and optimizes - <quote>hidden</quote> equalities in joins. This includes - queries of the form - </para> -<programlisting> -SELECT * FROM t1,t2,t3 - WHERE t1.a=t2.a AND t2.a=t3.a -</programlisting> - - <para> - as well as - </para> - -<programlisting> -SELECT * FROM t1,t2 - WHERE t1.a=t2.c AND t1.b=t2.d AND t2.d BETWEEN i AND j; -</programlisting> - - <para> - where <literal>a</literal>, <literal>b</literal>, - <literal>c</literal>, and <literal>d</literal> are - indexed columns, and <literal>i</literal> and - <literal>j</literal> are constant values. - </para> - </listitem> - - <listitem> - <para> - Optimization of <literal>NOT IN</literal> and - <literal>NOT BETWEEN</literal> relations, reducing or - eliminating table scans for queries making use of these. - </para> - </listitem> - - <listitem> - <para> - The <literal>VARCHAR</literal> data type as implemented - in MySQL 5.0 is more efficient than in previous - versions, due to the elimination of the old (and - nonstandard) removal of trailing spaces during retrival. - </para> - </listitem> - - <listitem> - <para> - The addition of a true <literal>BIT</literal> column - type; this type is much more efficient for storage and - retrieval of Boolean values than the workarounds - required in MySQL in versions previous to 5.0. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Performance Improvements in the - <literal>InnoDB</literal> Storage Engine</emphasis>: - </para> - - <itemizedlist> - <listitem> - <para> - New compact storage format which can save up to 20% - of the disk space required in previous - MySQL/<literal>InnoDB</literal> versions. - </para> - </listitem> - - <listitem> - <para> - Faster recovery from a failed or aborted <literal>ALTER - TABLE</literal>. - </para> - </listitem> - - <listitem> - <para> - Faster implementation of <literal>TRUNCATE</literal>. - </para> - </listitem> - </itemizedlist> - - <para> - (See <xref linkend="innodb"/>.) - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Performance Improvements in the - <literal>NDBCluster</literal> Storage Engine</emphasis>: - </para> - - <itemizedlist> - <listitem> - <para> - Faster handling of queries that use - <literal>IN</literal> and <literal>BETWEEN</literal>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Condition pushdown</emphasis>: - In cases involving the comparison of an unindexed - column with a constant, this condition is - <quote>pushed down</quote> to the cluster where it - is evaluated in all partitions - simultaneously, eliminating the need to send - non-matching records over the network. This can make - such queries 10 to 100 times faster than in MySQL - 4.1 Cluster. - </para> - </listitem> - </itemizedlist> - - <para> - (See <xref linkend="ndbcluster"/>.) - </para> - </listitem> - - <listitem> - <para> - <literal>COUNT(DISTINCT)</literal> is made faster in - cases not involving <literal>BLOB</literal> columns - through the use of a temporary file rather than a - temporary table. - </para> - - <para> - <literal>MIN()</literal> and <literal>MAX()</literal> - with <literal>GROUP BY</literal> are also now better - optimized. - </para> - </listitem> - - <listitem> - <para> - The performance of the MySQL client library is increased - through the use of a receive buffer that greatly reduces - the number of system calls which the library needs to - make. This can speed up the retrieval of large result - sets by a factor of 2. - </para> - </listitem> - - <listitem> - <para> - Null keys can be <quote>pre-eliminated</quote> in many - cases, speeding up <literal>COUNT(*)</literal> queries. - An example of such a query might be - </para> - -<programlisting> -SELECT COUNT(*) FROM t1,t2 WHERE t2.c=t1.a; -</programlisting> - <para> - where <literal>c</literal> is an indexed column allowing - <literal>NULL</literal> values. - </para> - </listitem> - - </itemizedlist> - </listitem> - </itemizedlist> <para> - For more detailed information on changes in MySQL 5.0, see - <xref linkend="news-5-0-x"/>. + For more detailed information on changes in MySQL 5.0, see the + &title-refman-5-0;, available from the MySQL AB website. </para> <para> @@ -1339,13 +521,9 @@ available. See <xref linkend="installing-source-tree"/>. </para> - <remark role="todo"> - [js] Add nutshell-5-1 section. This needs to be done by the time - that 5.0 goes GA. - </remark> - </section> - + + </section> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../refman-common/information-sources.xml"/> Modified: trunk/refman-5.0/renamed-nodes.txt =================================================================== --- trunk/refman-5.0/renamed-nodes.txt 2005-10-19 10:22:27 UTC (rev 96) +++ trunk/refman-5.0/renamed-nodes.txt 2005-10-19 12:53:47 UTC (rev 97) @@ -75,3 +75,301 @@ windows-binary-installation windows-installation windows-prepare-environment windows-create-option-file windows-running windows-testing +mysql-4-0-nutshell ../4.1/en/mysql-4-0-nutshell +mysql-4-1-nutshell ../4.1/en/mysql-4-1-nutshell +nutshell-4-1-features ../4.1/en/nutshell-4-1-features +todo-mysql-5-0 mysql-5-0-nutshell +upgrading-from-4-0 ../4.1/en/upgrading-from-4-0 +upgrading-from-3-23 ../4.1/en/upgrading-from-3-23 +upgrading-from-3-22 ../4.1/en/upgrading-from-3-22 +upgrading-from-3-21 ../4.1/en/upgrading-from-3-21 +upgrading-from-3-20 ../4.1/en/upgrading-from-3-20 +downgrading-to-4-0 ../4.1/en/downgrading-to-4-0 +open-bsd-2-8 ../4.1/en/open-bsd-2-8 +news-4-1-x ../4.1/en/news-4-1-x +news-4-1-13 ../4.1/en/news-4-1-13 +news-4-1-12 ../4.1/en/news-4-1-12 +news-4-1-11 ../4.1/en/news-4-1-11 +news-4-1-10 ../4.1/en/news-4-1-10 +news-4-1-9 ../4.1/en/news-4-1-9 +news-4-1-8 ../4.1/en/news-4-1-8 +news-4-1-7 ../4.1/en/news-4-1-7 +news-4-1-6 ../4.1/en/news-4-1-6 +news-4-1-5 ../4.1/en/news-4-1-5 +news-4-1-4 ../4.1/en/news-4-1-4 +news-4-1-3 ../4.1/en/news-4-1-3 +news-4-1-2 ../4.1/en/news-4-1-2 +news-4-1-1 ../4.1/en/news-4-1-1 +news-4-1-0 ../4.1/en/news-4-1-0 +news 4-0-x ../4.1/en/news 4-0-x +news 4-0-25 ../4.1/en/news 4-0-25 +news 4-0-24 ../4.1/en/news 4-0-24 +news 4-0-23 ../4.1/en/news 4-0-23 +news 4-0-22 ../4.1/en/news 4-0-22 +news 4-0-21 ../4.1/en/news 4-0-21 +news 4-0-20 ../4.1/en/news 4-0-20 +news 4-0-19 ../4.1/en/news 4-0-19 +news 4-0-18 ../4.1/en/news 4-0-18 +news 4-0-17 ../4.1/en/news 4-0-17 +news 4-0-16 ../4.1/en/news 4-0-16 +news 4-0-15 ../4.1/en/news 4-0-15 +news 4-0-14 ../4.1/en/news 4-0-14 +news 4-0-13 ../4.1/en/news 4-0-13 +news 4-0-12 ../4.1/en/news 4-0-12 +news 4-0-11 ../4.1/en/news 4-0-11 +news 4-0-10 ../4.1/en/news 4-0-10 +news 4-0-9 ../4.1/en/news 4-0-9 +news 4-0-8 ../4.1/en/news 4-0-8 +news 4-0-7 ../4.1/en/news 4-0-7 +news 4-0-6 ../4.1/en/news 4-0-6 +news 4-0-5 ../4.1/en/news 4-0-5 +news 4-0-4 ../4.1/en/news 4-0-4 +news 4-0-3 ../4.1/en/news 4-0-3 +news 4-0-2 ../4.1/en/news 4-0-2 +news 4-0-1 ../4.1/en/news 4-0-1 +news 4-0-0 ../4.1/en/news 4-0-0 +news 3-23-x ../4.1/en/news 3-23-x +news 3-23-59 ../4.1/en/news 3-23-59 +news 3-23-58 ../4.1/en/news 3-23-58 +news 3-23-57 ../4.1/en/news 3-23-57 +news 3-23-56 ../4.1/en/news 3-23-56 +news 3-23-55 ../4.1/en/news 3-23-55 +news 3-23-54 ../4.1/en/news 3-23-54 +news 3-23-53 ../4.1/en/news 3-23-53 +news 3-23-52 ../4.1/en/news 3-23-52 +news 3-23-51 ../4.1/en/news 3-23-51 +news 3-23-50 ../4.1/en/news 3-23-50 +news 3-23-49 ../4.1/en/news 3-23-49 +news 3-23-48 ../4.1/en/news 3-23-48 +news 3-23-47 ../4.1/en/news 3-23-47 +news 3-23-46 ../4.1/en/news 3-23-46 +news 3-23-45 ../4.1/en/news 3-23-45 +news 3-23-44 ../4.1/en/news 3-23-44 +news 3-23-43 ../4.1/en/news 3-23-43 +news 3-23-42 ../4.1/en/news 3-23-42 +news 3-23-41 ../4.1/en/news 3-23-41 +news 3-23-40 ../4.1/en/news 3-23-40 +news 3-23-39 ../4.1/en/news 3-23-39 +news 3-23-38 ../4.1/en/news 3-23-38 +news 3-23-37 ../4.1/en/news 3-23-37 +news 3-23-36 ../4.1/en/news 3-23-36 +news 3-23-35 ../4.1/en/news 3-23-35 +news 3-23-34 ../4.1/en/news 3-23-34 +news 3-23-33 ../4.1/en/news 3-23-33 +news 3-23-32 ../4.1/en/news 3-23-32 +news 3-23-31 ../4.1/en/news 3-23-31 +news 3-23-30 ../4.1/en/news 3-23-30 +news 3-23-29 ../4.1/en/news 3-23-29 +news 3-23-28 ../4.1/en/news 3-23-28 +news 3-23-27 ../4.1/en/news 3-23-27 +news 3-23-26 ../4.1/en/news 3-23-26 +news 3-23-25 ../4.1/en/news 3-23-25 +news 3-23-24 ../4.1/en/news 3-23-24 +news 3-23-23 ../4.1/en/news 3-23-23 +news 3-23-22 ../4.1/en/news 3-23-22 +news 3-23-21 ../4.1/en/news 3-23-21 +news 3-23-20 ../4.1/en/news 3-23-20 +news 3-23-19 ../4.1/en/news 3-23-19 +news 3-23-18 ../4.1/en/news 3-23-18 +news 3-23-17 ../4.1/en/news 3-23-17 +news 3-23-16 ../4.1/en/news 3-23-16 +news 3-23-15 ../4.1/en/news 3-23-15 +news 3-23-14 ../4.1/en/news 3-23-14 +news 3-23-13 ../4.1/en/news 3-23-13 +news 3-23-12 ../4.1/en/news 3-23-12 +news 3-23-11 ../4.1/en/news 3-23-11 +news 3-23-10 ../4.1/en/news 3-23-10 +news 3-23-9 ../4.1/en/news 3-23-9 +news 3-23-8 ../4.1/en/news 3-23-8 +news 3-23-7 ../4.1/en/news 3-23-7 +news 3-23-6 ../4.1/en/news 3-23-6 +news 3-23-5 ../4.1/en/news 3-23-5 +news 3-23-4 ../4.1/en/news 3-23-4 +news 3-23-3 ../4.1/en/news 3-23-3 +news 3-23-2 ../4.1/en/news 3-23-2 +news 3-23-1 ../4.1/en/news 3-23-1 +news 3-23-0 ../4.1/en/news 3-23-0 +news 3-22-x ../4.1/en/news 3-22-x +news 3-22-35 ../4.1/en/news 3-22-35 +news 3-22-34 ../4.1/en/news 3-22-34 +news 3-22-33 ../4.1/en/news 3-22-33 +news 3-22-32 ../4.1/en/news 3-22-32 +news 3-22-31 ../4.1/en/news 3-22-31 +news 3-22-30 ../4.1/en/news 3-22-30 +news 3-22-29 ../4.1/en/news 3-22-29 +news 3-22-28 ../4.1/en/news 3-22-28 +news 3-22-27 ../4.1/en/news 3-22-27 +news 3-22-26 ../4.1/en/news 3-22-26 +news 3-22-25 ../4.1/en/news 3-22-25 +news 3-22-24 ../4.1/en/news 3-22-24 +news 3-22-23 ../4.1/en/news 3-22-23 +news 3-22-22 ../4.1/en/news 3-22-22 +news 3-22-21 ../4.1/en/news 3-22-21 +news 3-22-20 ../4.1/en/news 3-22-20 +news 3-22-19 ../4.1/en/news 3-22-19 +news 3-22-18 ../4.1/en/news 3-22-18 +news 3-22-17 ../4.1/en/news 3-22-17 +news 3-22-16 ../4.1/en/news 3-22-16 +news 3-22-15 ../4.1/en/news 3-22-15 +news 3-22-14 ../4.1/en/news 3-22-14 +news 3-22-13 ../4.1/en/news 3-22-13 +news 3-22-12 ../4.1/en/news 3-22-12 +news 3-22-11 ../4.1/en/news 3-22-11 +news 3-22-10 ../4.1/en/news 3-22-10 +news 3-22-9 ../4.1/en/news 3-22-9 +news 3-22-8 ../4.1/en/news 3-22-8 +news 3-22-7 ../4.1/en/news 3-22-7 +news 3-22-6 ../4.1/en/news 3-22-6 +news 3-22-5 ../4.1/en/news 3-22-5 +news 3-22-4 ../4.1/en/news 3-22-4 +news 3-22-3 ../4.1/en/news 3-22-3 +news 3-22-2 ../4.1/en/news 3-22-2 +news 3-22-1 ../4.1/en/news 3-22-1 +news 3-22-0 ../4.1/en/news 3-22-0 +news 3-21-x ../4.1/en/news 3-21-x +news 3-21-33 ../4.1/en/news 3-21-33 +news 3-21-32 ../4.1/en/news 3-21-32 +news 3-21-31 ../4.1/en/news 3-21-31 +news 3-21-30 ../4.1/en/news 3-21-30 +news 3-21-29 ../4.1/en/news 3-21-29 +news 3-21-28 ../4.1/en/news 3-21-28 +news 3-21-27 ../4.1/en/news 3-21-27 +news 3-21-26 ../4.1/en/news 3-21-26 +news 3-21-25 ../4.1/en/news 3-21-25 +news 3-21-24 ../4.1/en/news 3-21-24 +news 3-21-23 ../4.1/en/news 3-21-23 +news 3-21-22 ../4.1/en/news 3-21-22 +news 3-21-21 ../4.1/en/news 3-21-21 +news 3-21-20 ../4.1/en/news 3-21-20 +news 3-21-19 ../4.1/en/news 3-21-19 +news 3-21-18 ../4.1/en/news 3-21-18 +news 3-21-17 ../4.1/en/news 3-21-17 +news 3-21-16 ../4.1/en/news 3-21-16 +news 3-21-15 ../4.1/en/news 3-21-15 +news 3-21-14b ../4.1/en/news 3-21-14b +news 3-21-14a ../4.1/en/news 3-21-14a +news 3-21-13 ../4.1/en/news 3-21-13 +news 3-21-12 ../4.1/en/news 3-21-12 +news 3-21-11 ../4.1/en/news 3-21-11 +news 3-21-10 ../4.1/en/news 3-21-10 +news 3-21-9 ../4.1/en/news 3-21-9 +news 3-21-8 ../4.1/en/news 3-21-8 +news 3-21-7 ../4.1/en/news 3-21-7 +news 3-21-6 ../4.1/en/news 3-21-6 +news 3-21-5 ../4.1/en/news 3-21-5 +news 3-21-4 ../4.1/en/news 3-21-4 +news 3-21-3 ../4.1/en/news 3-21-3 +news 3-21-2 ../4.1/en/news 3-21-2 +news 3-21-1 ../4.1/en/news 3-21-1 +news 3-21-0 ../4.1/en/news 3-21-0 +news 3-20-x ../4.1/en/news 3-20-x +news 3-20-18 ../4.1/en/news 3-20-18 +news 3-20-17 ../4.1/en/news 3-20-17 +news 3-20-16 ../4.1/en/news 3-20-16 +news 3-20-15 ../4.1/en/news 3-20-15 +news 3-20-14 ../4.1/en/news 3-20-14 +news 3-20-13 ../4.1/en/news 3-20-13 +news 3-20-12 ../4.1/en/news 3-20-12 +news 3-20-11 ../4.1/en/news 3-20-11 +news 3-20-10 ../4.1/en/news 3-20-10 +news 3-20-9 ../4.1/en/news 3-20-9 +news 3-20-8 ../4.1/en/news 3-20-8 +news 3-20-7 ../4.1/en/news 3-20-7 +news 3-20-6 ../4.1/en/news 3-20-6 +news 3-20-5 ../4.1/en/news 3-20-5 +news 3-20-4 ../4.1/en/news 3-20-4 +news 3-20-3 ../4.1/en/news 3-20-3 +news 3-20-2 ../4.1/en/news 3-20-2 +news 3-20-1 ../4.1/en/news 3-20-1 +news 3-20-0 ../4.1/en/news 3-20-0 +news 3-19-x ../4.1/en/news 3-19-x +news 3-19-5 ../4.1/en/news 3-19-5 +news 3-19-4 ../4.1/en/news 3-19-4 +news 3-19-3 ../4.1/en/news 3-19-3 +innodb-change-history ../4.1/en/innodb-change-history +innodb-news-4-1-14 ../4.1/en/innodb-news-4-1-14 +innodb-news-4-1-13 ../4.1/en/innodb-news-4-1-13 +innodb-news-4-1-12 ../4.1/en/innodb-news-4-1-12 +innodb-news-4-1-11 ../4.1/en/innodb-news-4-1-11 +innodb-news-4-1-10 ../4.1/en/innodb-news-4-1-10 +innodb-news-4-1-9 ../4.1/en/innodb-news-4-1-9 +innodb-news-4-1-8 ../4.1/en/innodb-news-4-1-8 +innodb-news-4-1-7 ../4.1/en/innodb-news-4-1-7 +innodb-news-4-1-6 ../4.1/en/innodb-news-4-1-6 +innodb-news-4-1-5 ../4.1/en/innodb-news-4-1-5 +innodb-news-4-1-4 ../4.1/en/innodb-news-4-1-4 +innodb-news-4-1-3 ../4.1/en/innodb-news-4-1-3 +innodb-news-4-1-2 ../4.1/en/innodb-news-4-1-2 +innodb-news-4-1-1 ../4.1/en/innodb-news-4-1-1 +innodb-news-4-1-0 ../4.1/en/innodb-news-4-1-0 +innodb-news-4-0-21 ../4.1/en/innodb-news-4-0-21 +innodb-news-4-0-20 ../4.1/en/innodb-news-4-0-20 +innodb-news-4-0-19 ../4.1/en/innodb-news-4-0-19 +innodb-news-4-0-18 ../4.1/en/innodb-news-4-0-18 +innodb-news-4-0-17 ../4.1/en/innodb-news-4-0-17 +innodb-news-4-0-16 ../4.1/en/innodb-news-4-0-16 +innodb-news-4-0-15 ../4.1/en/innodb-news-4-0-15 +innodb-news-4-0-14 ../4.1/en/innodb-news-4-0-14 +innodb-news-4-0-13 ../4.1/en/innodb-news-4-0-13 +innodb-news-4-0-12 ../4.1/en/innodb-news-4-0-12 +innodb-news-4-0-11 ../4.1/en/innodb-news-4-0-11 +innodb-news-4-0-10 ../4.1/en/innodb-news-4-0-10 +innodb-news-4-0-9 ../4.1/en/innodb-news-4-0-9 +innodb-news-4-0-8 ../4.1/en/innodb-news-4-0-8 +innodb-news-4-0-7 ../4.1/en/innodb-news-4-0-7 +innodb-news-4-0-6 ../4.1/en/innodb-news-4-0-6 +innodb-news-4-0-5 ../4.1/en/innodb-news-4-0-5 +innodb-news-4-0-4 ../4.1/en/innodb-news-4-0-4 +innodb-news-4-0-3 ../4.1/en/innodb-news-4-0-3 +innodb-news-4-0-2 ../4.1/en/innodb-news-4-0-2 +innodb-news-4-0-1 ../4.1/en/innodb-news-4-0-1 +innodb-news-3-23-58 ../4.1/en/innodb-news-3-23-58 +innodb-news-3-23-57 ../4.1/en/innodb-news-3-23-57 +innodb-news-3-23-56 ../4.1/en/innodb-news-3-23-56 +innodb-news-3-23-55 ../4.1/en/innodb-news-3-23-55 +innodb-news-3-23-54 ../4.1/en/innodb-news-3-23-54 +innodb-news-3-23-53 ../4.1/en/innodb-news-3-23-53 +innodb-news-3-23-52 ../4.1/en/innodb-news-3-23-52 +innodb-news-3-23-51 ../4.1/en/innodb-news-3-23-51 +innodb-news-3-23-50 ../4.1/en/innodb-news-3-23-50 +innodb-news-3-23-49 ../4.1/en/innodb-news-3-23-49 +innodb-news-3-23-48 ../4.1/en/innodb-news-3-23-48 +innodb-news-3-23-47 ../4.1/en/innodb-news-3-23-47 +innodb-news-3-23-46 ../4.1/en/innodb-news-3-23-46 +innodb-news-3-23-45 ../4.1/en/innodb-news-3-23-45 +innodb-news-3-23-44 ../4.1/en/innodb-news-3-23-44 +innodb-news-3-23-43 ../4.1/en/innodb-news-3-23-43 +innodb-news-3-23-42 ../4.1/en/innodb-news-3-23-42 +innodb-news-3-23-41 ../4.1/en/innodb-news-3-23-41 +innodb-news-3-23-40 ../4.1/en/innodb-news-3-23-40 +innodb-news-3-23-39 ../4.1/en/innodb-news-3-23-39 +innodb-news-3-23-38 ../4.1/en/innodb-news-3-23-38 +mysql-cluster-news-4-1-13 ../4.1/en/mysql-cluster-news-4-1-13 +mysql-cluster-news-4-1-12 ../4.1/en/mysql-cluster-news-4-1-12 +mysql-cluster-news-4-1-11 ../4.1/en/mysql-cluster-news-4-1-11 +mysql-cluster-news-4-1-10 ../4.1/en/mysql-cluster-news-4-1-10 +mysql-cluster-news-4-1-9 ../4.1/en/mysql-cluster-news-4-1-9 +mysql-cluster-news-4-1-8 ../4.1/en/mysql-cluster-news-4-1-8 +mysql-cluster-news-4-1-7 ../4.1/en/mysql-cluster-news-4-1-7 +mysql-cluster-news-4-1-6 ../4.1/en/mysql-cluster-news-4-1-6 +mysql-cluster-news-4-1-5 ../4.1/en/mysql-cluster-news-4-1-5 +mysql-cluster-news-4-1-4 ../4.1/en/mysql-cluster-news-4-1-4 +mysql-cluster-news-4-1-3 ../4.1/en/mysql-cluster-news-4-1-3 +charset-upgrading ../4.1/en/charset-upgrading +charset-map ../4.1/en/charset-map +charset-conversion ../4.1/en/charset-conversion +isam-storage-engine ../4.1/en/isam-storage-engine +innodb-in-mysql-3-23 ../4.1/en/innodb-in-mysql-3-23 +password-hashing-4-1-0 ../4.1/en/password-hashing-4-1-0 +update-log ../4.1/en/update-log +timestamp-pre-4-1 ../4.1/en/timestamp-pre-4-1 +replication-upgrade-4-0 ../4.1/en/replication-upgrade-4-0 +mysqlcc using-mysql-programs +todo mysql-5-0-nutshell +todo-mysql-5-0 mysql-5-0-nutshell +todo-mysql-5-1 mysql-5-0-nutshell +todo-future mysql-5-0-nutshell +todo-sometime mysql-5-0-nutshell +todo-unplanned mysql-5-0-nutshell +beos operating-system-specific-notes +open-bsd-2-8 operating-system-specific-notes \ No newline at end of file Modified: trunk/refman-5.1/introduction.xml =================================================================== --- trunk/refman-5.1/introduction.xml 2005-10-19 10:22:27 UTC (rev 96) +++ trunk/refman-5.1/introduction.xml 2005-10-19 12:53:47 UTC (rev 97) @@ -392,751 +392,20 @@ </tgroup> </informaltable> - <section id="mysql-4-0-nutshell"> - - <title id="title-mysql-4-0-nutshell">&title-mysql-4-0-nutshell;</title> - + <section id="mysql-5-1-nutshell"> + <title id="title-mysql-5-1-nutshell">&title-mysql-5-1-nutshell;</title> + <para> - MySQL 4.0 is available for download at - <ulink url="http://dev.mysql.com/"/> and from our mirrors. MySQL - 4.0 has been tested by a large number of users and is in - production use at many large sites. + For a list of features that we plan to add in MySQL 5.1, see + <xref linkend="roadmap"/>. We will add more detailed information + to this section as 5.1 development continues. </para> - - <section id="nutshell-4-0-features"> - - <title id="title-nutshell-4-0-features">&title-nutshell-4-0-features;</title> - - <itemizedlist> - - <listitem> - <para> - Speed enhancements - </para> - - <itemizedlist> - - <listitem> - <para> - MySQL 4.0 implemented a query cache that can give a - major speed boost to applications with repetitive - queries. See <xref linkend="query-cache"/>. - </para> - </listitem> - - <listitem> - <para> - Version 4.0 further increased the speed of MySQL - Server in a number of areas, such as bulk - <literal>INSERT</literal> statements, searching on - packed indexes, full-text searching (using - <literal>FULLTEXT</literal> indexes), and - <literal>COUNT(DISTINCT)</literal>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - Introduction of Embedded MySQL Server - </para> - - <itemizedlist> - - <listitem> - <para> - The Embedded Server library added in this release can - easily be used to create standalone and embedded - applications. The embedded server provides an - alternative to using MySQL in a client/server - environment. See - <xref linkend="nutshell-embedded-mysql"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <literal>InnoDB</literal> storage engine as standard - </para> - - <itemizedlist> - - <listitem> - <para> - The <literal>InnoDB</literal> storage engine began to - be offered as a standard feature of the MySQL server. - This provided full support for ACID transactions, - foreign keys with cascading <literal>UPDATE</literal> - and <literal>DELETE</literal>, and row-level locking - as standard features. See <xref linkend="innodb"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - New functionality - </para> - - <itemizedlist> - - <listitem> - <para> - The enhanced <literal>FULLTEXT</literal> search - capabilities of MySQL Server 4.0 enabled - <literal>FULLTEXT</literal> indexing of large text - masses with both binary and natural-language searching - logic. It became possible to customize minimal word - length and define your own stop word lists in most - human languages, enabling a broader class of - applications to be built with MySQL Server. See - <xref linkend="fulltext-search"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - Standards compliance, portability, and migration - </para> - - <itemizedlist> - - <listitem> - <para> - MySQL Server added support for the - <literal>UNION</literal> statement, a standard SQL - feature. - </para> - </listitem> - - <listitem> - <para> - Starting with version 4.0, MySQL runs natively on - Novell NetWare 6.0 and higher. See - <xref linkend="netware-installation"/>. - </para> - </listitem> - - <listitem> - <para> - Features to simplify migration from other database - systems to MySQL Server include <literal>TRUNCATE - TABLE</literal> (as in Oracle) - - <remark role="note"> - Commented out IDENTITY until someone explains what - it means... - </remark> - - - - <remark> - and IDENTITY as a synonym for automatically - incremented keys (as in Sybase) - </remark> - - . - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - Internationalization - </para> - - <itemizedlist> - - <listitem> - <para> - German-speaking users should note that MySQL 4.0 added - support for a new character set, - <literal>latin1_de</literal>, which ensures that words - with umlauts are sorted in the same order as in German - telephone books. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Usability enhancements</emphasis> - </para> - - <itemizedlist> - - <listitem> - <para> - As of Version 4.0, most <command>mysqld</command> - parameters (startup options) can be set without taking - down the server. This is a convenient feature for - database administrators. See - <xref linkend="set-option"/>. - </para> - </listitem> - - <listitem> - <para> - Multiple-table <literal>DELETE</literal> and - <literal>UPDATE</literal> statements were added. - </para> - </listitem> - - <listitem> - <para> - On Windows, symbolic link handling at the database - level was enabled by default. On Unix, the - <literal>MyISAM</literal> storage engine added support - for symbolic linking at the table level (and not just - the database level as before). - </para> - </listitem> - - <listitem> - <para> - The addition of the - <literal>SQL_CALC_FOUND_ROWS</literal> and - <literal>FOUND_ROWS()</literal> functions made 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> - - <para> - For a more comprehensive list of MySQL 4.0 features, see the - &title-refman-4-1;, available at the MySQL AB website, which - covers MySQL 4.1 and previous versions of the MySQL server - software. - </para> - - </section> - - <section id="nutshell-embedded-mysql"> - - <title id="title-nutshell-embedded-mysql">&title-nutshell-embedded-mysql;</title> - - <para> - The <literal>libmysqld</literal> embedded server library made - MySQL Server suitable for a wider range of applications. 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 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> - The embedded MySQL library uses the same interface as the - normal client library. See <xref linkend="libmysqld"/>. - Embedded MySQL is available under the same dual-licensing - model as the MySQL Server; see - <ulink url="http://www.mysql.com/company/legal/licensing/"/> - for more information. - </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> - - <section id="mysql-4-1-nutshell"> - - <title id="title-mysql-4-1-nutshell">&title-mysql-4-1-nutshell;</title> - + <para> - MySQL Server 4.0 laid the foundation for new features - implemented in MySQL 4.1, such as subqueries and Unicode - support, which were desired by many of our customers. + See also <xref linkend="partitioning"/>. </para> - - <para> - MySQL Server 4.1 is currently in production status, and binaries - are available for download at - <ulink url="http://dev.mysql.com/downloads/mysql/4.1.html"/>. - All binary releases pass our extensive test suite without any - errors on the platforms on which we test. See the - &title-refman-4-1;, available at the MySQL AB website for more - specific information. - </para> - - <para> - For those wishing to use the most recent development source for - MySQL 4.1, we also make our BitKeeper repositories publicly - available. See <xref linkend="installing-source-tree"/>. - </para> - - <section id="nutshell-4-1-features"> - - <title id="title-nutshell-4-1-features">&title-nutshell-4-1-features;</title> - - <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> - - <itemizedlist> - - <listitem> - <para> - <emphasis role="bold">Support for subqueries and derived - tables</emphasis>: - </para> - - <itemizedlist> - - <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> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Speed enhancements</emphasis>: - </para> - - <itemizedlist> - - <listitem> - <para> - Faster binary client/server protocol with support for - prepared statements and parameter binding. See - <xref linkend="c-api-prepared-statements"/>. - </para> - </listitem> - - <listitem> - <para> - <literal>BTREE</literal> indexing is supported for - <literal>HEAP</literal> tables, significantly - improving response time for non-exact searches. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Added functionality</emphasis>: - </para> - - <itemizedlist> - - <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> - The <literal>MyISAM</literal> storage engine added - support for OpenGIS spatial types for storing - geographical data. See - <xref linkend="spatial-extensions-in-mysql"/>. - </para> - </listitem> - - <listitem> - <para> - Support was added for replication over SSL - connections. - </para> - </listitem> - - <listitem> - <para> - Support for a number of additional storage engines was - implemented in the MySQL 4.1 release series: - - <itemizedlist> - - <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> - <literal>NDB Cluster</literal> is the storage - engine used by MySQL Cluster to implement tables - that are partitioned over many computers. See - <xref linkend="ndbcluster"/>. - </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>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>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> - - </itemizedlist> - - <emphasis role="bold">Note</emphasis>: These engines - 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> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Standards compliance, portability, - and migration</emphasis>: - </para> - - <itemizedlist> - - <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> - - <listitem> - <para> - <literal>SHOW WARNINGS</literal> shows warnings for - the last command. See <xref linkend="show-warnings"/>. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Internationalization and - Localization</emphasis>: - </para> - - <itemizedlist> - - <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> - 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> - Per-connection time zones support, allowing individual - clients to select their own time zones when necessary. - </para> - </listitem> - - </itemizedlist> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Usability enhancements</emphasis>: - </para> - - <itemizedlist> - - <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 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 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 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> - </listitem> - - </itemizedlist> - - <para> - For a more comprehensive list of MySQL 4.1 features, see the - &title-refman-4-1;, available at the MySQL AB website. - </para> - - </section> - </section> - <section id="mysql-5-0-nutshell"> - - <title id="title-mysql-5-0-nutshell">&title-mysql-5-0-nutshell;</title> - - <para> - The following features are implemented in MySQL 5.0. - </para> - - <itemizedlist> - - <listitem> - <para> - <emphasis role="bold"><literal>BIT</literal> Data - Type</emphasis>: Can be used to store numbers in binary - notation. See <xref linkend="numeric-type-overview"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Cursors</emphasis>: Elementary support - for server-side cursors. See <xref linkend="cursors"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Information - Schema</emphasis>: The introduction of the - <literal>INFORMATION_SCHEMA</literal> database in MySQL 5.0 - provided a standards-compliant means for accessing the MySQL - Server's metadata, that is, data about the databases - (schemas) on the server and the objects which they contain. - See <xref linkend="information-schema"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Instance Manager</emphasis>: Can be - used to start and stop the MySQL Server, even from a remote - host. See <xref linkend="instance-manager"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Precision Math</emphasis>: MySQL 5.0 - introduced stricter criteria for acceptance or rejection of - data, and implemented a new library for fixed-point - arithmetic. These contributed to a much higher degree of - accuracy for mathematical operations and greater control - over invalid values. See <xref linkend="precision-math"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Storage Engines</emphasis>: Storage - engines added in MySQL 5.0 include - <literal>ARCHIVE</literal> and <literal>FEDERATED</literal>. - See <xref linkend="archive-storage-engine"/> and - <xref linkend="federated-storage-engine"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Stored Routines</emphasis>: Support - for named stored procedures and stored functions was - implemented in MySQL 5.0. See - <xref linkend="stored-procedures"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Strict Mode and Standard Error - Handling</emphasis>: MySQL 5.0 added a strict mode where by - it follows standard SQL in a number of ways in which it did - not previously. Support for standard SQLSTATE error messages - was also implemented. See <xref linkend="server-sql-mode"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Triggers</emphasis>: MySQL 5.0 added - limited support for triggers. See <xref linkend="triggers"/> - and <xref linkend="ansi-diff-triggers"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold"><literal>VARCHAR</literal> Data - Type</emphasis>: The maximum effective length of a - <literal>VARCHAR</literal> column was increased to 65,532 - bytes, and stripping of trailing whitespace was eliminated. - See <xref linkend="string-types"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">Views</emphasis>: MySQL 5.0 added - support for named, updateable views. See - <xref linkend="views"/> and - <xref linkend="ansi-diff-views"/>. - </para> - </listitem> - - <listitem> - <para> - <emphasis role="bold">XA Transactions</emphasis>: See - <xref linkend="xa"/>. - </para> - </listitem> - - </itemizedlist> - - <para> - For more detailed information on changes in MySQL 5.0, see the - &title-refman-5-0;, available from the MySQL AB website. - </para> - - <para> - For those wishing to take a look at the bleeding edge of MySQL - development, we make our BitKeeper repository for MySQL publicly - available. See <xref linkend="installing-source-tree"/>. - </para> - - <remark role="todo"> - [js] Add nutshell-5-1 section. This needs to be done by the time - that 5.0 goes GA. - </remark> - - </section> - </section> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../refman-common/information-sources.xml"/> Modified: trunk/refman-common/titles.en.ent =================================================================== --- trunk/refman-common/titles.en.ent 2005-10-19 10:22:27 UTC (rev 96) +++ trunk/refman-common/titles.en.ent 2005-10-19 12:53:47 UTC (rev 97) @@ -708,6 +708,7 @@ <!ENTITY title-mysql-4-1-nutshell "MySQL 4.1 in a Nutshell"> <!ENTITY title-mysql-5-0-cluster-changes "MySQL Cluster Changes in MySQL 5.0"> <!ENTITY title-mysql-5-0-nutshell "What's New in MySQL 5.0"> +<!ENTITY title-mysql-5-1-nutshell "What's New in MySQL 5.1"> <!ENTITY title-mysql-5-1-cluster-roadmap "MySQL 5.1 Development Roadmap for MySQL Cluster"> <!ENTITY title-mysql-affected-rows "<literal>mysql_affected_rows()</literal>"> <!ENTITY title-mysql-apis "MySQL APIs and Libraries">
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r97 - in trunk: refman-5.0 refman-5.1 refman-common | jstephens | 19 Oct |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 1.343 sec. using MySQL 5.1.14-beta-log