From: jon Date: February 3 2007 9:41am Subject: svn commit - mysqldoc@docsrva: r4777 - branches/telcos/refman-5.1 List-Archive: http://lists.mysql.com/commits/19291 Message-Id: <200702030941.l139fjaJ020020@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2007-02-03 10:41:34 +0100 (Sat, 03 Feb 2007) New Revision: 4777 Log: Reformat. Modified: branches/telcos/refman-5.1/apis-c.xml branches/telcos/refman-5.1/client-utility-programs.xml branches/telcos/refman-5.1/connectors-apis.xml branches/telcos/refman-5.1/database-administration.xml branches/telcos/refman-5.1/functions.xml branches/telcos/refman-5.1/information-schema.xml branches/telcos/refman-5.1/installing.xml branches/telcos/refman-5.1/introduction.xml branches/telcos/refman-5.1/mysql-cluster.xml branches/telcos/refman-5.1/news-5.1.xml branches/telcos/refman-5.1/partitioning.xml branches/telcos/refman-5.1/porting.xml branches/telcos/refman-5.1/problems.xml branches/telcos/refman-5.1/restrictions.xml branches/telcos/refman-5.1/se-innodb.xml branches/telcos/refman-5.1/se-myisam.xml branches/telcos/refman-5.1/sql-syntax.xml branches/telcos/refman-5.1/storage-engines.xml Modified: branches/telcos/refman-5.1/apis-c.xml =================================================================== --- branches/telcos/refman-5.1/apis-c.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/apis-c.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 550 bytes @@ -12572,8 +12572,8 @@ - When inserting multiple values, the last automatically incremented value - is returned. + When inserting multiple values, the last automatically + incremented value is returned. Modified: branches/telcos/refman-5.1/client-utility-programs.xml =================================================================== --- branches/telcos/refman-5.1/client-utility-programs.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/client-utility-programs.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 1, Lines Deleted: 3; 721 bytes @@ -11463,9 +11463,7 @@ newline at the end of each line. The format can be specified explicitly using the - and - - options. + and options. Modified: branches/telcos/refman-5.1/connectors-apis.xml =================================================================== --- branches/telcos/refman-5.1/connectors-apis.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/connectors-apis.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 2, Lines Added: 6, Lines Deleted: 6; 1319 bytes @@ -146,9 +146,9 @@ - The C API provides low-level access to the MySQL protocol through - the libmysqlclient library; this is the - primary method used to connect to an instance of the MySQL + The C API provides low-level access to the MySQL protocol + through the libmysqlclient library; this is + the primary method used to connect to an instance of the MySQL server, and is used both by MySQL command line clients and many of the APIs also detailed in this section. @@ -156,9 +156,9 @@ - libmysqld is an embedded MySQL server library that enables you - to embed an instance of the MySQL server into your C - applications. + libmysqld is an embedded MySQL server library + that enables you to embed an instance of the MySQL server into + your C applications. Modified: branches/telcos/refman-5.1/database-administration.xml =================================================================== --- branches/telcos/refman-5.1/database-administration.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/database-administration.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 3, Lines Added: 6, Lines Deleted: 3; 1289 bytes @@ -4603,7 +4603,8 @@ is NO, the server can use only statement-based logging. See . This variable was - added in MySQL 5.1.5, and was removed in MySQL 5.1.15/NDB-6.1.1. + added in MySQL 5.1.5, and was removed in MySQL + 5.1.15/NDB-6.1.1. @@ -6325,7 +6326,8 @@ - Beginning with MySQL 5.1.15/NDB-6.1.1, the following conditions apply: + Beginning with MySQL 5.1.15/NDB-6.1.1, the following + conditions apply: @@ -29318,7 +29320,8 @@ - It refers to user-defined functions (UDFs) or stored functions. + It refers to user-defined functions (UDFs) or stored + functions. Modified: branches/telcos/refman-5.1/functions.xml =================================================================== --- branches/telcos/refman-5.1/functions.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/functions.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 3, Lines Deleted: 2; 841 bytes @@ -7050,8 +7050,9 @@ - Beginning with MySQL 5.1.15/NDB-6.1.1, DATE_FORMAT() returns a - string with a character set and collation given by + Beginning with MySQL 5.1.15/NDB-6.1.1, + DATE_FORMAT() returns a string with a + character set and collation given by character_set_connection and collation_connection so that it can return month and weekday names containing non-ASCII characters. Modified: branches/telcos/refman-5.1/information-schema.xml =================================================================== --- branches/telcos/refman-5.1/information-schema.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/information-schema.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 8, Lines Added: 19, Lines Deleted: 19; 4224 bytes @@ -4971,7 +4971,7 @@ was added in MySQL 5.1.6. - + Beginning with MySQL 5.1.14, an additional row is present in @@ -4981,12 +4981,12 @@ row, the value of the FILE_ID column is always 0, that of the FILE_TYPE column is always UNDO - FILE, and that of the STATUS + FILE, and that of the STATUS column is always NORMAL. In MySQL ¤t-series; the value of the ENGINE column is always ndbcluster. - + This row shows in the FREE_EXTENTS column the total number of free extents available to all undo files @@ -4994,13 +4994,13 @@ shown in the LOGFILE_GROUP_NAME and LOGFILE_GROUP_NUMBER columns, respectively. - + Suppose there are no existing log file groups on your MySQL Cluster, and you create one using the following statement: - - + + mysql> CREATE LOGFILE GROUP lg1 -> ADD UNDOFILE 'undofile.dat' -> INITIAL_SIZE = 16M @@ -5008,13 +5008,13 @@ -> ENGINE = NDB; Query OK, 0 rows affected (3.81 sec) - + You can now see this NULL row when you - query the FILES table: + query the FILES table: - - + + mysql> SELECT DISTINCT -> FILE_NAME AS File, -> FREE_EXTENTS AS Free, @@ -5030,7 +5030,7 @@ +--------------+---------+---------+------+----------+ 2 rows in set (0.01 sec) - + The total number of free extents available for undo logging is always somewhat less than the sum of the @@ -5040,8 +5040,8 @@ second undo file to the log file group, then repeating the previous query against the FILES table: - - + + mysql> ALTER LOGFILE GROUP lg1 -> ADD UNDOFILE 'undofile02.dat' -> INITIAL_SIZE = 4M @@ -5064,15 +5064,15 @@ +----------------+---------+---------+------+----------+ 3 rows in set (0.01 sec) - + The amount of free space in bytes which is available for undo logging by Disk Data tables using this log file group can be approximated by multiplying the number of free extents by the initial size: - - + + mysql> SELECT -> FREE_EXTENTS AS 'Free Extents', -> FREE_EXTENTS * EXTENT_SIZE AS 'Free Bytes' @@ -5086,14 +5086,14 @@ +--------------+------------+ 1 row in set (0.02 sec) - + If you create a Disk Data table and then insert some rows into it, you can see approximately how much space remains for undo logging afterwards, for example: - - + + mysql> CREATE TABLESPACE ts1 -> ADD DATAFILE 'data1.dat' -> USE LOGFILE GROUP lg1 Modified: branches/telcos/refman-5.1/installing.xml =================================================================== --- branches/telcos/refman-5.1/installing.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/installing.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 2, Lines Added: 5, Lines Deleted: 4; 1233 bytes @@ -8249,8 +8249,8 @@ mysqld to be disabled. For Windows, the configure.js script recognizes the DISABLE_GRANT_OPTIONS flag, which has the - same effect. The capability is available beginning with MySQL - 5.1.15/NDB-6.1.1. + same effect. The capability is available beginning with + MySQL 5.1.15/NDB-6.1.1. @@ -12228,8 +12228,9 @@ - Incompatible change: Beginning with - MySQL 5.1.15/NDB-6.1.1, the following conditions apply to enabling the + Incompatible change: + Beginning with MySQL 5.1.15/NDB-6.1.1, the following + conditions apply to enabling the read_only system variable: Modified: branches/telcos/refman-5.1/introduction.xml =================================================================== --- branches/telcos/refman-5.1/introduction.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/introduction.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 17, Lines Deleted: 16; 3022 bytes @@ -168,31 +168,32 @@ Next para also appears in preface.xml - + This is the Reference Manual for the MySQL Database System ¤t-series;, through release ¤t-version;. Although it contains references to older releases, it is not intended for use with any other version of the MySQL software due to functional and - other differences between MySQL ¤t-series; and those versions. - If you are not using MySQL ¤t-series;, please refer to the - version of the Manual appropriate to the version which you are - using, which can be found on the MySQL web site at + other differences between MySQL ¤t-series; and those + versions. If you are not using MySQL ¤t-series;, please + refer to the version of the Manual appropriate to the version + which you are using, which can be found on the MySQL web site at . MySQL ¤t-series; branched from the main MySQL development tree beginning with MySQL 5.1.14, - and are distinguished from the mainline versions by the addition of + and are distinguished from the mainline versions by the addition + of NDB-x.y.z - to the version string. The first part of the version string (before - the slash character) represents the the mainline MySQL release from - which the ¤t-series; release was branched, and may be the same - for different ¤t-series; releases. The second part of the - version string (following the slash character) denotes the NDB - storage engine version, which is different for each ¤t-series; - release. The first release of MySQL ¤t-series; was MySQL - 5.1.14/NDB-6.1.0-beta. The current release for MySQL - ¤t-series; is MySQL ¤t-version;. + to the version string. The first part of the version string + (before the slash character) represents the the mainline MySQL + release from which the ¤t-series; release was branched, and + may be the same for different ¤t-series; releases. The + second part of the version string (following the slash character) + denotes the NDB storage engine version, which is different for + each ¤t-series; release. The first release of MySQL + ¤t-series; was MySQL 5.1.14/NDB-6.1.0-beta. The current + release for MySQL ¤t-series; is MySQL ¤t-version;. - + All information appearing in this Manual that relates to MySQL versions 5.1.14 and earlier also applies to ¤t-series; Modified: branches/telcos/refman-5.1/mysql-cluster.xml =================================================================== --- branches/telcos/refman-5.1/mysql-cluster.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/mysql-cluster.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 4, Lines Added: 15, Lines Deleted: 15; 3397 bytes @@ -12703,7 +12703,7 @@ directory. This program reads the files created as a result of the backup and inserts the stored information into the database. - + ndb_restore must be executed once for each of the backup files that were created by the START @@ -17339,14 +17339,14 @@ the two ALTER TABLESPACE ... DROP DATAFILE statements may be executed in either order. - + You can obtain information about data files used by Disk Data tables by querying the FILES table in the INFORMATION_SCHEMA database. An extra NULL row was added to this table in MySQL 5.1.14 for providing additional information about undo - log files. For more information and examples of use, see + log files. For more information and examples of use, see . @@ -19519,7 +19519,7 @@ schemes. This feature is also available for many other MySQL storage engines, which support additional partitioning types that are not available with NDB Cluster - tables. + tables. @@ -19536,32 +19536,32 @@ . - + Autodiscovery of table schema - changes. In MySQL 5.1, you no longer need to + changes. In MySQL 5.1, you no longer need to issue FLUSH TABLES or a - dummy SELECT in order for - new NDB tables or changes made to schemas of - existing NDB tables on one SQL node to be - visible on the cluster's other SQL nodes. + dummy SELECT in order for + new NDB tables or changes made to schemas + of existing NDB tables on one SQL node to + be visible on the cluster's other SQL nodes. - + Note: When creating a new database, it is still necessary to issue the CREATE - DATABASE or CREATE SCHEMA + DATABASE or CREATE SCHEMA statement on each SQL node in the cluster. - + - See + See MySQL - Cluster issues from previous versions that have been resolved in + Cluster issues from previous versions that have been resolved in MySQL 5.1 for more information. Modified: branches/telcos/refman-5.1/news-5.1.xml =================================================================== --- branches/telcos/refman-5.1/news-5.1.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/news-5.1.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 13, Lines Added: 39, Lines Deleted: 36; 6136 bytes @@ -21,7 +21,7 @@ - An overview of features added in MySQL 5.1 can be found here: + An overview of features added in MySQL 5.1 can be found here: . @@ -57,44 +57,47 @@ This section documents all changes and bug fixes that have been applied in the second MySQL ¤t-series; Beta release — also known as MySQL Cluster - 5.1.15/NDB-6.1.1 — since the release of MySQL + 5.1.15/NDB-6.1.1 — since the release of MySQL Cluster 5.1.14/NDB-6.1.0. This version also incorporates all bugfixes and feature changes which were added in the mainline - 5.1.15 release; information about these can be found in + 5.1.15 release; information about these can be found in . - - + + - Upgrading to MySQL 5.1.15/NDB-6.1.1 from a previous - release - + Upgrading to MySQL 5.1.15/NDB-6.1.1 from a previous release + + + This release is not binary compatible with any previous - releases. This means that: - + releases. This means that: + + You cannot perform an online upgrade to this release from either MySQL 5.1.14/NDB-6.1.0 or from any of the mainline MySQL 5.1 releases. You must shut down the cluster, replace all binaries, then restart the cluster. - + - - + + You must recompile any MySQL Cluster API applications used with a previous version of MySQL Cluster. This includes all NDB API and MGM API applications. + - + Functionality added or changed: @@ -140,11 +143,11 @@ - + A memory leak could cause problems during a node or cluster - shutdown or failure. (Bug #25997) + shutdown or failure. (Bug #25997) @@ -155,7 +158,7 @@ failures. (Bug #25755) - + Hosts in clusters with a large number of nodes could @@ -163,7 +166,7 @@ data. (Bug #25711) - + When stopping and restarting multiple data nodes, the last @@ -171,7 +174,7 @@ #19645) - + Cluster APIs / @@ -186,8 +189,8 @@ - An element could sometimes be inserted twice into the - hash table, causing a data node to crash. (Bug #25286) + An element could sometimes be inserted twice into the hash + table, causing a data node to crash. (Bug #25286) @@ -405,7 +408,7 @@ - + If there was insufficient memory available to @@ -413,7 +416,7 @@ server to hang during startup. (Bug #24751) - + Using row-based replication to replicate to a table having at @@ -422,7 +425,7 @@ slave to fail. (Bug #24490) - + Optimizations that are legal only for subqueries without @@ -430,24 +433,24 @@ for any subquery without tables. (Bug #24670) - + A query using WHERE - unsigned_column NOT IN - ('negative_value') - could cause the server to crash. (Bug #24261) + unsigned_column NOT IN + ('negative_value') could + cause the server to crash. (Bug #24261) - + A FETCH statement using a cursor on a table which was not in the table cache could sometimes cause the - server to crash. (Bug #24117) + server to crash. (Bug #24117) - + CREATE TABLE ... SELECT statements were not @@ -1533,8 +1536,8 @@ This section documents all changes and bug fixes that have been - applied in the first MySQL ¤t-series; Beta release - (also known as MySQL Cluster 5.1.14/NDB-6.1.0), and since MySQL + applied in the first MySQL ¤t-series; Beta release (also + known as MySQL Cluster 5.1.14/NDB-6.1.0), and since MySQL ¤t-series; diverged from MySQL 5.1.14 standard. @@ -4330,15 +4333,15 @@ REPAIR TABLE tbl_name QUICK; - + An invalid GRANT statement for which Ok was returned on a replication master caused an error on the slave and replication to fail. (Bug - #6774) + #6774) - + Modified: branches/telcos/refman-5.1/partitioning.xml =================================================================== --- branches/telcos/refman-5.1/partitioning.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/partitioning.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 11, Lines Added: 29, Lines Deleted: 27; 5946 bytes @@ -21,7 +21,7 @@ partitioning - + This chapter discusses user-defined @@ -291,8 +291,8 @@ Note: MySQL partitioning cannot be used with the MERGE or CSV storage engines. Beginning with MySQL - 5.1.15/NDB-6.1.1, FEDERATED tables also cannot be - partitioned (Bug #22451). Prior to MySQL 5.1.6, it was also not + 5.1.15/NDB-6.1.1, FEDERATED tables also cannot + be partitioned (Bug #22451). Prior to MySQL 5.1.6, it was also not feasible to create a partitioned table using the BLACKHOLE storage engine (Bug #14524). Partitioning by KEY is supported for use with @@ -2813,7 +2813,7 @@ ALTER TABLE ... DROP PARTITION. It does, however, support the other partitioning-related extensions to ALTER TABLE that are described in this - chapter. + chapter. @@ -4032,10 +4032,10 @@ expression consists of an equality or a range which can be reduced to a set of equalities, or when the partitioning expression represents an increasing or decreasing relationship. Pruning can - also be applied for tables partitioned on a DATE or - DATETIME column when the partitioning - expression uses the YEAR() or - TO_DAYS() function. + also be applied for tables partitioned on a + DATE or DATETIME column when + the partitioning expression uses the YEAR() or + TO_DAYS() function. (Note: We plan to add pruning support in a future MySQL release for additional functions that act on a DATE or DATETIME @@ -4711,12 +4711,12 @@ Partitioning maximum number of partitions - + The maximum number of partitions possible for a given table is 1024. This includes subpartitions. - + If, when creating tables with a very large number of partitions (but which is less than the maxmimum stated @@ -4733,7 +4733,7 @@ partitioning and foreign keys - + Partitioned tables do not support foreign keys. This includes partitioned tables employing the InnoDB @@ -4746,6 +4746,7 @@ partitioning and FULLTEXT indexes + Partitioned tables do not support FULLTEXT indexes. This includes partitioned tables employing the @@ -4765,6 +4766,7 @@ partitioning and temporary tables + As of MySQL 5.1.8, temporary tables cannot be partitioned. (Bug #17497) @@ -4781,13 +4783,13 @@ Tables using the MERGE storage engine cannot be partitioned. - + Partitioning of FEDERATED tables is not - supported. Beginning with MySQL 5.1.15/NDB-6.1.1, it is not possible to - create partitioned FEDERATED tables at all. - We are working to remove this limitation in a future MySQL - release. + supported. Beginning with MySQL 5.1.15/NDB-6.1.1, it is not + possible to create partitioned FEDERATED + tables at all. We are working to remove this limitation in a + future MySQL release. @@ -4816,10 +4818,10 @@ - When performing an upgrade, tables which are partitioned by - KEY and that use any storage engine other than - NDBCLUSTER and must be dumped and - reloaded. + When performing an upgrade, tables which are partitioned by + KEY and that use any storage engine other + than NDBCLUSTER and must be dumped and + reloaded. @@ -4840,13 +4842,13 @@ - The lone exception to this restriction occurs when partitioning - by [LINEAR] KEY — - where it is possible to use columns of other types types as - partitioning keys — because MySQL's internal key-hashing - functions produce the correct data type from these types. For - example, the following CREATE TABLE - statement is valid: + The lone exception to this restriction occurs when + partitioning by [LINEAR] + KEY — where it is possible to use + columns of other types types as partitioning keys — + because MySQL's internal key-hashing functions produce the + correct data type from these types. For example, the following + CREATE TABLE statement is valid: Modified: branches/telcos/refman-5.1/porting.xml =================================================================== --- branches/telcos/refman-5.1/porting.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/porting.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 860 bytes @@ -78,17 +78,17 @@ HP-UX aCC, IBM AIX xlC_r), Intel ecc/icc and Compaq cxx). - + icc and MySQL Cluster support> - + MySQL Cluster compiling with icc - + Important: If you are trying to build MySQL 5.1 with icc on the IA64 platform, Modified: branches/telcos/refman-5.1/problems.xml =================================================================== --- branches/telcos/refman-5.1/problems.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/problems.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 1, Lines Deleted: 1; 710 bytes @@ -907,7 +907,7 @@ The number of connections allowed is controlled by the - max_connections system variable. Beginning + max_connections system variable. Beginning with MySQL 5.1.15, its default value is 151 to improve performance when MySQL is used with the Apache Web server. (Previously, the default was 100.) If you need to support more Modified: branches/telcos/refman-5.1/restrictions.xml =================================================================== --- branches/telcos/refman-5.1/restrictions.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/restrictions.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 2, Lines Added: 2, Lines Deleted: 2; 664 bytes @@ -279,9 +279,10 @@ - Stored routines and triggers in MySQL Cluster + + Stored functions, stored procedures, and triggers are all supported by tables using the NDB storage @@ -336,7 +337,6 @@ - Modified: branches/telcos/refman-5.1/se-innodb.xml =================================================================== --- branches/telcos/refman-5.1/se-innodb.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/se-innodb.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 2, Lines Deleted: 2; 930 bytes @@ -3689,8 +3689,8 @@ Deadlock occurs here because client A needs an X lock to delete the row. However, - that lock request cannot be granted because client B already - has a request for an X lock and is + that lock request cannot be granted because client B already has + a request for an X lock and is waiting for client A to release its S lock. Nor can the S lock held by A be upgraded to an X lock because of the Modified: branches/telcos/refman-5.1/se-myisam.xml =================================================================== --- branches/telcos/refman-5.1/se-myisam.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/se-myisam.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 2, Lines Deleted: 0; 486 bytes @@ -913,6 +913,8 @@ Note + + While a compressed table is read-only, and you cannot therefore update or add rows in the table, DDL (Data Modified: branches/telcos/refman-5.1/sql-syntax.xml =================================================================== --- branches/telcos/refman-5.1/sql-syntax.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/sql-syntax.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 1, Lines Added: 5, Lines Deleted: 5; 1027 bytes @@ -12668,13 +12668,13 @@ CREATE INDEX, which do cause a commit.) - - + + - Beginning with MySQL 5.1.15/NDB-6.1.1, CREATE TABLE ... - SELECT causes an implicit commit before and + Beginning with MySQL 5.1.15/NDB-6.1.1, CREATE TABLE + ... SELECT causes an implicit commit before and after the statement is executed. However, no commit occurs - for CREATE TEMPORARY TABLE ... SELECT. + for CREATE TEMPORARY TABLE ... SELECT. Modified: branches/telcos/refman-5.1/storage-engines.xml =================================================================== --- branches/telcos/refman-5.1/storage-engines.xml 2007-02-03 09:23:29 UTC (rev 4776) +++ branches/telcos/refman-5.1/storage-engines.xml 2007-02-03 09:41:34 UTC (rev 4777) Changed blocks: 4, Lines Added: 8, Lines Deleted: 7; 1993 bytes @@ -91,10 +91,10 @@ This chapter describes each of the MySQL storage engines except for NDB Cluster, which is covered in . It also contains a description of - the pluggable storage engine architecture (see + the pluggable storage engine architecture (see ). - + For answers to some commonly asked questions about MySQL storage engines, see . @@ -118,8 +118,8 @@ - The MySQL pluggable storage engine architecture is shown in - . + The MySQL pluggable storage engine architecture is shown in + .
@@ -873,8 +873,8 @@ mdbtools — A pluggable storage engine that allows read-only - access to Microsoft Access .mdb database - files. + access to Microsoft Access .mdb + database files. @@ -898,7 +898,8 @@ For more information on developing a customer storage engine that can be used with the Pluggable Storage Engine Architecture, - see , in the MySQL Internals manual. + see , in the MySQL Internals + manual.