From: paul Date: December 9 2005 12:38am Subject: svn commit - mysqldoc@docsrva: r529 - in trunk: . refman-5.0 refman-5.1 refman-common List-Archive: http://lists.mysql.com/commits/51 Message-Id: <200512090038.jB90cLB5005035@docsrva.mysql.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Author: paul Date: 2005-12-09 01:38:20 +0100 (Fri, 09 Dec 2005) New Revision: 529 Log: r4632@frost: paul | 2005-12-08 18:37:59 -0600 Document bugfixes: 11555 14233 15441 15510 15028 15512 13293 13421 14155 14780 14221 14902 Modified: trunk/ trunk/refman-5.0/stored-procedures.xml trunk/refman-5.1/stored-procedures.xml trunk/refman-common/news-4.1.xml trunk/refman-common/news-5.0.xml trunk/refman-common/news-5.1.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4626 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1505 + b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:4632 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:1505 Modified: trunk/refman-5.0/stored-procedures.xml =================================================================== --- trunk/refman-5.0/stored-procedures.xml 2005-12-08 20:44:14 UTC (rev 528) +++ trunk/refman-5.0/stored-procedures.xml 2005-12-09 00:38:20 UTC (rev 529) @@ -111,6 +111,13 @@ + The server manipulates the mysql.proc table in + response to statements that create, alter, or drop stored + routines. It is not supported that the server will notice manual + manipulation of this table. + + + Beginning with MySQL 5.0.3, the grant system has been modified to take stored routines into account as follows: Modified: trunk/refman-5.1/stored-procedures.xml =================================================================== --- trunk/refman-5.1/stored-procedures.xml 2005-12-08 20:44:14 UTC (rev 528) +++ trunk/refman-5.1/stored-procedures.xml 2005-12-09 00:38:20 UTC (rev 529) @@ -111,6 +111,13 @@ + The server manipulates the mysql.proc table in + response to statements that create, alter, or drop stored + routines. It is not supported that the server will notice manual + manipulation of this table. + + + In MySQL ¤t-series;, the grant system takes stored routines into account as follows: Modified: trunk/refman-common/news-4.1.xml =================================================================== --- trunk/refman-common/news-4.1.xml 2005-12-08 20:44:14 UTC (rev 528) +++ trunk/refman-common/news-4.1.xml 2005-12-09 00:38:20 UTC (rev 529) @@ -159,10 +159,21 @@ Functionality added or changed: - - ADD AN ITEMIZED LIST WHEN WE HAVE SOME ITEMS THAT GO HERE - + + + + In the latin5_turkish_ci collation, the + order of the characters A WITH CIRCUMFLEX, + I WITH CIRCUMLEX, and U WITH + CIRCUMFLEX was changed. If you have used these + characters in any indexed columns, you should rebuild those + indexes. (Bug#13421) + + + + + Bugs fixed: @@ -171,6 +182,15 @@ + Multiple-table update operations were counting updates and not + updated rows. As a result, if a row had several updates it was + counted several times for the rows matched + value but updated only once. (Bug #15028) + + + + + SELECT queries that began with an opening parenthesis were not being placed in the query cache. (Bug #14652) @@ -276,6 +296,18 @@ + Portability fixes to support OpenSSL 0.9.8a. (Bug #14221) + + + + + + Closed a memory leak in the SSL code. (Bug #14780) + + + + + Perform character set conversion of constant values whenever possible without data loss. (Bug #10446) Modified: trunk/refman-common/news-5.0.xml =================================================================== --- trunk/refman-common/news-5.0.xml 2005-12-08 20:44:14 UTC (rev 528) +++ trunk/refman-common/news-5.0.xml 2005-12-09 00:38:20 UTC (rev 529) @@ -204,10 +204,18 @@ Bugs fixed: - - ADD AN ITEMIZED LIST WHEN WE HAVE SOME ITEMS THAT GO HERE - + + + + Resolution of the argument to the VALUES() + function to a variable inside a stored routine caused a server + crash. The argument must be a table column. (Bug #15441) + + + + +
@@ -252,6 +260,17 @@ + + + In the latin5_turkish_ci collation, the + order of the characters A WITH CIRCUMFLEX, + I WITH CIRCUMLEX, and U WITH + CIRCUMFLEX was changed. If you have used these + characters in any indexed columns, you should rebuild those + indexes. (Bug#13421) + + + @@ -262,6 +281,67 @@ + ANALYZE TABLE did not properly update table + statistics for a MyISAM table with a + FULLTEXT index containing stopwords, so a + subsequent ANALYZE TABLE would not + recognize the table as having already been analyzed. (Bug + #14902) + + + + + + The maximum value of MAX_ROWS was handled + incorrectly on 64-bit systems. (Bug #14155) + + + + + + NDB Cluster: A forced cluster shutdown + occurred when the management daemon was restarted with a + changed config.ini file that added an + API/SQL node. (Bug #15512) + + + + + + Multiple-table update operations were counting updates and not + updated rows. As a result, if a row had several updates it was + counted several times for the rows matched + value but updated only once. (Bug #15028) + + + + + + A statement that produced a warning, when fetched via + mysql_stmt_fetch(), did not produce a + warning count according to + mysql_warning_count(). (Bug #15510) + + + + + + Manual manipulation of the mysql.proc table + could cause a server crash. This should not happen, but it is + also not supported that the server will notice such changes. + (Bug #14233) + + + + + + Revised table locking locking to allow proper assessment of + view security. (Bug #11555) + + + + + Within a stored procedure, inserting with INSERT … SELECT into a table with an AUTO_INCREMENT column did not generate the @@ -849,6 +929,16 @@ + InnoDB: When dropping and adding a + PRIMARY KEY, if a loose index scan using + only the second part of multiple-part index was chosen, + incorrect keys were created and an endless loop resulted. (Bug + #13293) + + + + + NDB Cluster: Repeated transactions using unique index lookups could cause a memory leak leading to error 288, Out of index operations in transaction Modified: trunk/refman-common/news-5.1.xml =================================================================== --- trunk/refman-common/news-5.1.xml 2005-12-08 20:44:14 UTC (rev 528) +++ trunk/refman-common/news-5.1.xml 2005-12-09 00:38:20 UTC (rev 529) @@ -84,6 +84,33 @@ + ANALYZE TABLE did not properly update table + statistics for a MyISAM table with a + FULLTEXT index containing stopwords, so a + subsequent ANALYZE TABLE would not + recognize the table as having already been analyzed. (Bug + #14902) + + + + + + The maximum value of MAX_ROWS was handled + incorrectly on 64-bit systems. (Bug #14155) + + + + + + Multiple-table update operations were counting updates and not + updated rows. As a result, if a row had several updates it was + counted several times for the rows matched + value but updated only once. (Bug #15028) + + + + + SELECT queries that began with an opening parenthesis were not being placed in the query cache. (Bug #14652) @@ -202,118 +229,119 @@ Functionality added or changed: - + This is the first public alpha release of the current MySQL 5.1 - development branch, providing an insight to upcoming features. While - some of these are still under heavy development, this release includes - the following new features and changes (in comparison to the current - MySQL 5.0 production release): + development branch, providing an insight to upcoming features. + While some of these are still under heavy development, this + release includes the following new features and changes (in + comparison to the current MySQL 5.0 production release): - + - + - Partitioning: - allows distributing portions of individual tables - across a filesystem, according to rules which can be set when the - table is created. In effect, different portions of a table are stored - as separate tables in different locations, but from the user - point of view, the partitioned table is still a single table. See - for further + Partitioning: allows + distributing portions of individual tables across a + filesystem, according to rules which can be set when the table + is created. In effect, different portions of a table are + stored as separate tables in different locations, but from the + user point of view, the partitioned table is still a single + table. See for further information on this functionality. (Author: Mikael Ronström) - + - Plugin API: - MySQL 5.1 will add support for a very flexible plugin API that will - allow the loading and unloading of various components at runtime, - without restarting the server. While the work on this are not finished - yet, pluggable full-text parsers - are a first step in this direction. - This allows users to implement their own input filter on the indexed - text, enabling full-text search capability on arbitrary data like PDF - files or other document formats. A pre-parser full-text plugin - performs the actual parsing and extraction of the text and hands it - over to the builtin MySQL full-text search. - (Author: Sergey Vojtovich) + Plugin API: MySQL 5.1 will + add support for a very flexible plugin API that will allow the + loading and unloading of various components at runtime, + without restarting the server. While the work on this are not + finished yet, pluggable full-text parsers + are a first step in this direction. This allows users to + implement their own input filter on the indexed text, enabling + full-text search capability on arbitrary data like PDF files + or other document formats. A pre-parser full-text plugin + performs the actual parsing and extraction of the text and + hands it over to the builtin MySQL full-text search. (Author: + Sergey Vojtovich) - + - The Instance Manager (IM) - now has some additional functionality: - + The Instance Manager (IM) now + has some additional functionality: + - + - SHOW instance_name LOG FILES - provides a listing of all log files used by the instance. (Author: Petr Chardin) - + SHOW instance_name + LOG FILES provides a listing of all log files + used by the instance. (Author: Petr Chardin) + - + - SHOW instance_name - LOG {ERROR | SLOW | GENERAL} size - retrieves a part of the specified log file. (Author: Petr Chardin) + SHOW instance_name + LOG {ERROR | SLOW | GENERAL} + size retrieves a + part of the specified log file. (Author: Petr Chardin) - + SET instance_name. option_name=option_value - sets an option to - the specified value and writes it to the config file - See for - more details on these new commands. (Author: Petr Chardin) + sets an option to the specified value and writes it to + the config file See + for more details on these new commands. (Author: Petr + Chardin) - + - - Two new aggregate functions, STDDEV_POP - and STDDEV_SAMP, for computing - the population and sample standard deviation of expressions. - See - for more info. (Author: Sergey Vojtovich) + Two new aggregate functions, STDDEV_POP + and STDDEV_SAMP, for computing the + population and sample standard deviation of expressions. See + for more info. (Author: + Sergey Vojtovich) - + - The performance of boolean full-text searches (using the + - Operator) has been improved. See - - for more details about full-text searching. - (Author: Sergey Vojtovich) + The performance of boolean full-text searches (using the + + Operator) has been improved. See + for more details about + full-text searching. (Author: Sergey Vojtovich) - + - VARCHAR fields used in MySQL Cluster - tables are now variable-sized; - that is, they now only allocate as much space as required to store - the data. Previously, a VARCHAR(n) - column allocated n+2 bytes (aligned - to 4 bytes), regardless if the actual inserted value required that - much space. (In other words, a VARCHAR column always required the - same, fixed, amount of storage as a CHAR column of the same size.) + VARCHAR fields used in MySQL Cluster tables + are now variable-sized; that is, they now only allocate as + much space as required to store the data. Previously, a + VARCHAR(n) + column allocated n+2 bytes (aligned to 4 bytes), regardless if + the actual inserted value required that much space. (In other + words, a VARCHAR column always required the + same, fixed, amount of storage as a CHAR + column of the same size.) - + Renamed the table_cache system variable to