From: jon Date: December 14 2006 5:20am Subject: svn commit - mysqldoc@docsrva: r4248 - in trunk: refman-4.1 refman-5.0 refman-5.1 List-Archive: http://lists.mysql.com/commits/16928 Message-Id: <200612140520.kBE5Kd6O019098@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: jstephens Date: 2006-12-14 06:20:37 +0100 (Thu, 14 Dec 2006) New Revision: 4248 Log: Reformat. Modified: trunk/refman-4.1/news-4.1.xml trunk/refman-5.0/releasenotes-es-5.0.xml trunk/refman-5.1/news-5.1.xml Modified: trunk/refman-4.1/news-4.1.xml =================================================================== --- trunk/refman-4.1/news-4.1.xml 2006-12-14 05:18:21 UTC (rev 4247) +++ trunk/refman-4.1/news-4.1.xml 2006-12-14 05:20:37 UTC (rev 4248) Changed blocks: 6, Lines Added: 18, Lines Deleted: 17; 3420 bytes @@ -198,27 +198,27 @@ - + ALTER ENABLE KEYS or ALTER TABLE - DISABLE KEYS combined with another ALTER - TABLE option other than RENAME - TO did nothing. In addition, if ALTER TABLE - was used on a table having disabled keys, the keys of the - resulting table were enabled. (Bug #24395) + DISABLE KEYS combined with another ALTER + TABLE option other than RENAME TO + did nothing. In addition, if ALTER TABLE was used on a table + having disabled keys, the keys of the resulting table were + enabled. (Bug #24395) - + Queries using a column alias in an expression as part of an ORDER BY clause failed, an example of such a query being SELECT mycol + 1 AS mynum FROM mytable - ORDER BY 30 - mynum. (Bug #22457) + ORDER BY 30 - mynum. (Bug #22457) - + Trailing spaces were not removed from Unicode @@ -227,15 +227,15 @@ affect the results of some ORDER BY queries that made use of such indexes. - + Note: When upgrading, it is necessary to re-create any existing indexes on Unicode CHAR columns in order to take advantage of the fix. This can be done by using a REPAIR - TABLE statement on each affected table. + TABLE statement on each affected table. - + (Bug #22052) @@ -498,7 +498,7 @@ - + If the user specified the server options @@ -507,9 +507,10 @@ , a warning would be given in some cases that some values were recalculated, with the result that - could be assigned greater value. + could be assigned greater + value. - + It should be noted that, in such cases, both the warning and the increase in the value @@ -518,7 +519,7 @@ the maximum number of open files, since this is determined by the operating system. - + The recalculation code has now been fixed to ensure that the value of is no longer @@ -526,7 +527,7 @@ if some values had to be decreased due to operating system limits. - + (Bug #21915) Modified: trunk/refman-5.0/releasenotes-es-5.0.xml =================================================================== --- trunk/refman-5.0/releasenotes-es-5.0.xml 2006-12-14 05:18:21 UTC (rev 4247) +++ trunk/refman-5.0/releasenotes-es-5.0.xml 2006-12-14 05:20:37 UTC (rev 4248) Changed blocks: 9, Lines Added: 37, Lines Deleted: 34; 7025 bytes @@ -56,30 +56,32 @@ - + NDB Cluster: It is now possible to create a unique hashed index on a column that is not defined as NOT NULL. Note that this change - applies only to tables using the NDB - storage engine. + applies only to tables using the NDB + storage engine. - + Unique indexes on columns in NDB tables do not store null values because they are mapped to primary keys in an internal index table (and primary keys cannot contain nulls). + Normally, an additional ordered index is created when one - creates unique indexes on NDB table columns; - this can be used to search for NULL values. - However, if USING HASH is specified when - such an index is created, no ordered index is created. + creates unique indexes on NDB table + columns; this can be used to search for + NULL values. However, if USING + HASH is specified when such an index is created, no + ordered index is created. - + The reason for permitting unique hash indexes with null values is that, in some cases, the user wants to save space if a @@ -89,16 +91,16 @@ MySQL does not support indexes that are not allowed to be searched in some cases, the NDB storage engine uses a full table scan with pushed conditions for the - referenced index columns to return the correct result. + referenced index columns to return the correct result. - + Note that a warning is returned if one creates a unique nullable hash index, since the query optimizer should be provided a hint not to use it with NULL values if this can be avoided. - + (Bug #21507) @@ -142,17 +144,17 @@ - + It was possible to use DATETIME values whose year, month, and day parts were all zeroes but whose hour, minute, and second parts contained nonzero values, an example of such an illegal DATETIME being - '0000-00-00 11:23:45'. (Bug #21789) + '0000-00-00 11:23:45'. (Bug #21789) - + It was possible to set the backslash character @@ -161,38 +163,38 @@ possible to use it as the delimiter. (Bug #21412) - + The loose index scan optimization for GROUP - BY with MIN or + BY with MIN or MAX was not applied within other queries, such as CREATE TABLE ... SELECT ..., INSERT ... SELECT ..., or in the FROM clauses of subqueries. (Bug #24156) - + ALTER ENABLE KEYS or ALTER TABLE - DISABLE KEYS combined with another ALTER - TABLE option other than RENAME - TO did nothing. In addition, if ALTER TABLE - was used on a table having disabled keys, the keys of the - resulting table were enabled. (Bug #24395) + DISABLE KEYS combined with another ALTER + TABLE option other than RENAME TO + did nothing. In addition, if ALTER TABLE was used on a table + having disabled keys, the keys of the resulting table were + enabled. (Bug #24395) - + Queries using a column alias in an expression as part of an ORDER BY clause failed, an example of such a query being SELECT mycol + 1 AS mynum FROM mytable - ORDER BY 30 - mynum. (Bug #22457) + ORDER BY 30 - mynum. (Bug #22457) - + Trailing spaces were not removed from Unicode @@ -201,15 +203,15 @@ affect the results of some ORDER BY queries that made use of such indexes. - + Note: When upgrading, it is necessary to re-create any existing indexes on Unicode CHAR columns in order to take advantage of the fix. This can be done by using a REPAIR - TABLE statement on each affected table. + TABLE statement on each affected table. - + (Bug #22052) @@ -688,7 +690,7 @@ - + If the user specified the server options @@ -697,9 +699,10 @@ , a warning would be given in some cases that some values were recalculated, with the result that - could be assigned greater value. + could be assigned greater + value. - + It should be noted that, in such cases, both the warning and the increase in the value @@ -708,7 +711,7 @@ the maximum number of open files, since this is determined by the operating system. - + The recalculation code has now been fixed to ensure that the value of is no longer @@ -716,7 +719,7 @@ if some values had to be decreased due to operating system limits. - + (Bug #21915) Modified: trunk/refman-5.1/news-5.1.xml =================================================================== --- trunk/refman-5.1/news-5.1.xml 2006-12-14 05:18:21 UTC (rev 4247) +++ trunk/refman-5.1/news-5.1.xml 2006-12-14 05:20:37 UTC (rev 4248) Changed blocks: 11, Lines Added: 48, Lines Deleted: 45; 9072 bytes @@ -138,17 +138,17 @@ - + It was possible to use DATETIME values whose year, month, and day parts were all zeroes but whose hour, minute, and second parts contained nonzero values, an example of such an illegal DATETIME being - '0000-00-00 11:23:45'. (Bug #21789) + '0000-00-00 11:23:45'. (Bug #21789) - + It was possible to set the backslash character @@ -157,18 +157,18 @@ possible to use it as the delimiter. (Bug #21412) - + ALTER ENABLE KEYS or ALTER TABLE - DISABLE KEYS combined with another ALTER - TABLE option other than RENAME - TO did nothing. In addition, if ALTER TABLE - was used on a table having disabled keys, the keys of the - resulting table were enabled. (Bug #24395) + DISABLE KEYS combined with another ALTER + TABLE option other than RENAME TO + did nothing. In addition, if ALTER TABLE was used on a table + having disabled keys, the keys of the resulting table were + enabled. (Bug #24395) - + An ALTER TABLE statement that used a @@ -188,24 +188,23 @@ against the renamed table would fail. (Bug #22369) - + Queries of the form SELECT ... WHERE - string = - ANY(...) failed when the server used a single-byte - character set and the client used a multi-byte character set. - (Bug #20835) + string = ANY(...) failed + when the server used a single-byte character set and the + client used a multi-byte character set. (Bug #20835) - + A partitioned table that used the DATA - DIRECTORY option, where the data directory was the + DIRECTORY option, where the data directory was the same as the directory in which the table definition file resided, became corrupted following ALTER TABLE - ENGINE=ARCHIVE. This was actually due to an issue + ENGINE=ARCHIVE. This was actually due to an issue with the ARCHIVE storage engine, and not with partitioned tables in general. (Bug #22634) @@ -504,30 +503,32 @@ . - + NDB Cluster: It is now possible to create a unique hashed index on a column that is not defined as NOT NULL. Note that this change - applies only to tables using the NDB - storage engine. + applies only to tables using the NDB + storage engine. - + Unique indexes on columns in NDB tables do not store null values because they are mapped to primary keys in an internal index table (and primary keys cannot contain nulls). + Normally, an additional ordered index is created when one - creates unique indexes on NDB table columns; - this can be used to search for NULL values. - However, if USING HASH is specified when - such an index is created, no ordered index is created. + creates unique indexes on NDB table + columns; this can be used to search for + NULL values. However, if USING + HASH is specified when such an index is created, no + ordered index is created. - + The reason for permitting unique hash indexes with null values is that, in some cases, the user wants to save space if a @@ -537,16 +538,16 @@ MySQL does not support indexes that are not allowed to be searched in some cases, the NDB storage engine uses a full table scan with pushed conditions for the - referenced index columns to return the correct result. + referenced index columns to return the correct result. - + Note that a warning is returned if one creates a unique nullable hash index, since the query optimizer should be provided a hint not to use it with NULL values if this can be avoided. - + (Bug #21507) @@ -612,36 +613,36 @@ - + CREATE FUNCTION X() and CREATE - FUNCTION Y() failed with a syntax error instead of + FUNCTION Y() failed with a syntax error instead of warning the user that these function names are already used (for GIS functions). (Bug #21015) - + The loose index scan optimization for GROUP - BY with MIN or + BY with MIN or MAX was not applied within other queries, such as CREATE TABLE ... SELECT ..., INSERT ... SELECT ..., or in the FROM clauses of subqueries. (Bug #24156) - + Queries using a column alias in an expression as part of an ORDER BY clause failed, an example of such a query being SELECT mycol + 1 AS mynum FROM mytable - ORDER BY 30 - mynum. (Bug #22457) + ORDER BY 30 - mynum. (Bug #22457) - + Trailing spaces were not removed from Unicode @@ -650,19 +651,20 @@ affect the results of some ORDER BY queries that made use of such indexes. - + Note: When upgrading, it is necessary to re-create any existing indexes on Unicode CHAR columns in order to take advantage of the fix. This can be done by using a REPAIR - TABLE statement on each affected table. + TABLE statement on each affected table. - + (Bug #22052) + NDB Cluster (Replication): If errors @@ -1257,7 +1259,7 @@ - + If the user specified the server options @@ -1266,9 +1268,10 @@ , a warning would be given in some cases that some values were recalculated, with the result that - could be assigned greater value. + could be assigned greater + value. - + It should be noted that, in such cases, both the warning and the increase in the value @@ -1277,7 +1280,7 @@ the maximum number of open files, since this is determined by the operating system. - + The recalculation code has now been fixed to ensure that the value of is no longer @@ -1285,7 +1288,7 @@ if some values had to be decreased due to operating system limits. - + (Bug #21915)