| List: | Internals | « Previous MessageNext Message » | |
| From: | mhillyer | Date: | June 22 2005 2:22am |
| Subject: | bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.2848) | ||
| View as plain text | |||
Below is the list of changes that have just been committed into a local mysqldoc repository of root. When root does a push these changes will be propagated to the main repository and, within 24 hours after the push, to the public repository. For information on how to access the public repository see http://www.mysql.com/doc/I/n/Installing_source_tree.html ChangeSet 1.2848 05/06/21 18:22:44 Mike.Hillyer@stripped +3 -0 Bug #7448 Bug #7858 Bug #7894 Bug #8135 Bug #8367 Bug #8610 Bug #9334 Bug #11298 refman/news.xml 1.12 05/06/21 18:22:43 Mike.Hillyer@stripped +169 -125 Bug #7448 Bug #7858 Bug #7894 Bug #8135 Bug #8367 Bug #8610 Bug #9334 Bug #11298 refman-5.0/news.xml 1.8 05/06/21 18:22:43 Mike.Hillyer@stripped +169 -125 Bug #7448 Bug #7858 Bug #7894 Bug #8135 Bug #8367 Bug #8610 Bug #9334 Bug #11298 refman-4.1/news.xml 1.8 05/06/21 18:22:43 Mike.Hillyer@stripped +169 -125 Bug #7448 Bug #7858 Bug #7894 Bug #8135 Bug #8367 Bug #8610 Bug #9334 Bug #11298 # This is a BitKeeper patch. What follows are the unified diffs for the # set of deltas contained in the patch. The rest of the patch, the part # that BitKeeper cares about, is below these diffs. # User: Mike.Hillyer # Host: www.openwin.org # Root: /home/mysqldoc/mysqldoc --- 1.7/refman-4.1/news.xml 2005-06-21 11:17:31 -06:00 +++ 1.8/refman-4.1/news.xml 2005-06-21 18:22:43 -06:00 @@ -225,22 +225,22 @@ Functionality added or changed: </para> - <itemizedlist> + <itemizedlist> - <listitem> - <para>New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal> - Prevents automatic substitution of storage engine when the requested - storage engine is disabled or not compiled in. (Bug #6877)</para> - </listitem> - - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit.</para> - </listitem> + <listitem><para> + New <literal>SQL_MODE</literal> - + <literal>NO_ENGINE_SUBSTITUTION</literal> Prevents automatic + substitution of storage engine when the requested storage engine is + disabled or not compiled in. (Bug #6877) + </para></listitem> - </itemizedlist> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. + </para></listitem> + + </itemizedlist> <para> Bugs fixed: @@ -248,49 +248,57 @@ <itemizedlist> - <listitem> - <para>An <literal>ORDER BY</literal> clause sometimes had no - effect on the ordering of a result when selecting specific columns - (as opposed to using <literal>SELECT *</literal>) from a view. - (Bug#7422)</para> - </listitem> - - <listitem> - <para>Some data definition statements (<literal>CREATE - TABLE</literal> where the table was not a temporary table, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were - not being written to the binary log after a - <literal>ROLLBACK</literal>. This also caused problems with - replication. (Bug#6883)</para> - </listitem> - - - <listitem> - <para>Calling a stored procedure that made use of an - <literal>INSERT ... SELECT ... UNION SELECT ...</literal> query - caused a server crash. (Bug#11060)</para> - </listitem> - - <listitem> - <para>Selecting from a view defined using <literal>SELECT - SUM(DISTINCT ...)</literal> caused an error; attempting to execute - a <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query - after defining such a view crashed the server. (Bug#7015)</para> - </listitem> - - <listitem> - <para>The <command>mysql</command> client would output a prompt - twice following input of very long strings, because it incorrectly - assumed that a call to the <command>_cgets()</command> function - would clear the input buffer. (Bug#10840) - </para> - </listitem> - - <listitem><para> - A three byte buffer overflow in the client functions caused improper - exiting of the client when reading a command from the user. (Bug - #10841) + <listitem><para> + Fixed hang/crash with Boolean full-text search against an unindexed + field for which the query contained more words than we allocated + space. (Bug #7858) + </para></listitem> + + <listitem><para> + Fixed column name generation in <literal>VIEW</literal> creation to + ensure there are no duplicate column names. (Bug #7448) + </para></listitem> + + <listitem><para> + An <literal>ORDER BY</literal> clause sometimes had no effect on + the ordering of a result when selecting specific columns (as + opposed to using <literal>SELECT *</literal>) from a view. + (Bug#7422) + </para></listitem> + + <listitem><para> + Some data definition statements (<literal>CREATE TABLE</literal> + where the table was not a temporary table, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal>) were not being written to the + binary log after a <literal>ROLLBACK</literal>. This also caused + problems with replication. (Bug#6883) + </para></listitem> + + <listitem><para> + Calling a stored procedure that made use of an <literal>INSERT ... + SELECT ... UNION SELECT ...</literal> query caused a server crash. + (Bug#11060) + </para></listitem> + + <listitem><para> + Selecting from a view defined using <literal>SELECT SUM(DISTINCT + ...)</literal> caused an error; attempting to execute a + <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query + after defining such a view crashed the server. (Bug#7015) + </para></listitem> + + <listitem><para> + The <command>mysql</command> client would output a prompt twice + following input of very long strings, because it incorrectly + assumed that a call to the <command>_cgets()</command> function + would clear the input buffer. (Bug#10840) + </para></listitem> + + <listitem><para> + A three byte buffer overflow in the client functions caused + improper exiting of the client when reading a command from the + user. (Bug #10841) </para></listitem> <listitem><para> @@ -445,14 +453,21 @@ <itemizedlist> -<listitem><para> - Everything you write after the <literal>DELIMITER</literal> keyword will be set as delimiter. Ex: <literal>DELIMITER -:;</literal> will set <literal>:;</literal> as the delimiter. This behavior is now consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) -</para></listitem> - -<listitem><para> - The <literal>table</literal>, <literal>type</literal>, and <literal>rows</literal> columns of <literal>EXPLAIN</literal> output can now be <literal>NULL</literal>. This is required for using <literal>EXPLAIN</literal> on <literal>SELECT</literal> queries that use no tables (i.e. <literal>EXPLAIN SELECT 1</literal>). (Bug #9899) -</para></listitem> + <listitem><para> + Everything you write after the <literal>DELIMITER</literal> keyword + will be set as delimiter. Ex: <literal>DELIMITER :;</literal> will + set <literal>:;</literal> as the delimiter. This behavior is now + consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) + </para></listitem> + + <listitem><para> + The <literal>table</literal>, <literal>type</literal>, and + <literal>rows</literal> columns of <literal>EXPLAIN</literal> + output can now be <literal>NULL</literal>. This is required for + using <literal>EXPLAIN</literal> on <literal>SELECT</literal> + queries that use no tables (i.e. <literal>EXPLAIN SELECT + 1</literal>). (Bug #9899) + </para></listitem> <listitem><para> Placeholders now can be used for <literal>LIMIT</literal> in @@ -512,9 +527,10 @@ <itemizedlist> -<listitem><para> - Fixed bug in <literal>FIELD()</literal> function where value list contains <literal>NULL</literal>. (Bug #10944) -</para></listitem> + <listitem><para> + Fixed bug in <literal>FIELD()</literal> function where value list + contains <literal>NULL</literal>. (Bug #10944) + </para></listitem> <listitem><para> Corrected a problem where an incorrect column type was returned in @@ -2358,8 +2374,8 @@ </para></listitem> <listitem><para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table + InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, single + table <literal>UPDATE…SELECT</literal> and single table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. @@ -4178,14 +4194,14 @@ file. </para></listitem> - <listitem> - <para>The <literal>table</literal>, <literal>type</literal>, and - <literal>rows</literal> columns of <literal>EXPLAIN</literal> - output can now be <literal>NULL</literal>. This is required for - using <literal>EXPLAIN</literal> on <literal>SELECT</literal> - queries that use no tables, such as - <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)</para> - </listitem> + <listitem><para> + The <literal>table</literal>, <literal>type</literal>, and + <literal>rows</literal> columns of <literal>EXPLAIN</literal> + output can now be <literal>NULL</literal>. This is required for + using <literal>EXPLAIN</literal> on <literal>SELECT</literal> + queries that use no tables, such as <literal>EXPLAIN SELECT + 1</literal>). (Bug #9899) + </para></listitem> </itemizedlist> @@ -4198,23 +4214,39 @@ <!-- NOTE: No need to start every item with "Fixed..."; sufficient to describe the issue that was fixed. --> - <listitem> - <para>The <command>mysql</command> client would output a prompt - twice following input of very long strings, because it incorrectly - assumed that a call to the <command>_cgets()</command> function - would clear the input buffer. (Bug#10840)</para> - </listitem> - - <listitem> - <para>A bug in <literal>FIELD()</literal> function caused the value - list to contain <literal>NULL</literal>. (Bug #10944)</para> - </listitem> - - <listitem> - <para>A three byte buffer overflow in the client functions could - cause improper exiting of the client when reading a command from - the user. (Bug #10841)</para> - </listitem> + <listitem><para> + OPTIMIZE of InnoDB table does not return 'Table is full' if out of + tablespace. (Bug #8135) + </para></listitem> + + <listitem><para> + GROUP BY queries with ROLLUP returned wrong results for expressions + containing group by columns. (Bug #7894) + </para></listitem> + + <listitem><para> + Fixed hang/crash with Boolean full-text search against an unindexed + field for which the query contained more words than we allocated + space. (Bug #7858) + </para></listitem> + + <listitem><para> + The <command>mysql</command> client would output a prompt twice + following input of very long strings, because it incorrectly + assumed that a call to the <command>_cgets()</command> function + would clear the input buffer. (Bug#10840) + </para></listitem> + + <listitem><para> + A bug in <literal>FIELD()</literal> function caused the value list + to contain <literal>NULL</literal>. (Bug #10944) + </para></listitem> + + <listitem><para> + A three byte buffer overflow in the client functions could cause + improper exiting of the client when reading a command from the + user. (Bug #10841) + </para></listitem> <listitem><para> Fixed a problem with the <literal>cp1250_czech_cs</literal> @@ -4496,9 +4528,9 @@ isolation level of the transaction is not set to serializable then <literal>InnoDB</literal> uses a consistent read for select in clauses like <literal>INSERT INTO…SELECT</literal> and - <literal>UPDATE…(SELECT)</literal> that do not specify - <literal>FOR UPDATE</literal> or <literal>IN SHARE MODE</literal>. - Thus no locks are set to rows read from selected table. + <literal>UPDATE…(SELECT)</literal> that do not specify <literal>FOR + UPDATE</literal> or <literal>IN SHARE MODE</literal>. Thus no locks + are set to rows read from selected table. </para></listitem> <listitem><para> @@ -5335,8 +5367,8 @@ <listitem><para> A join on two tables failed when each contained a <literal>BIGINT UNSIGNED</literal> column that were compared when their values - exceeded 2^63 - 1. The match failed and the join returned no - rows. (Bug #8562) + exceeded 2^63 - 1. The match failed and the join returned no rows. + (Bug #8562) </para></listitem> <listitem><para> @@ -5839,8 +5871,8 @@ </para></listitem> <listitem><para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table + InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, single + table <literal>UPDATE…SELECT</literal> and single table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. @@ -6647,12 +6679,11 @@ queries; unless <literal>--short-form</literal> is used. </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit.</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. + </para></listitem> </itemizedlist> @@ -6662,15 +6693,14 @@ <itemizedlist> - <listitem> - <para>Some data definition statements (<literal>CREATE - TABLE</literal> where the table was not a temporary table, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were - not being written to the binary log after a - <literal>ROLLBACK</literal>. This also caused problems with - replication. (Bug#6883)</para> - </listitem> + <listitem><para> + Some data definition statements (<literal>CREATE TABLE</literal> + where the table was not a temporary table, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal>) were not being written to the + binary log after a <literal>ROLLBACK</literal>. This also caused + problems with replication. (Bug#6883) + </para></listitem> <listitem><para> Fixed incorrect referencing to column by name from subquery to @@ -7094,9 +7124,9 @@ </para></listitem> <listitem><para> - InnoDB: Fixed a bug in <literal>LOAD DATA - INFILE…REPLACE</literal> printing duplicate key error when - executing the same load query several times. (Bug #5835) + InnoDB: Fixed a bug in <literal>LOAD DATA INFILE…REPLACE</literal> + printing duplicate key error when executing the same load query + several times. (Bug #5835) </para></listitem> <listitem><para> @@ -11014,9 +11044,9 @@ </para></listitem> <listitem><para> - InnoDB: Fixed a bug in <literal>LOAD DATA - INFILE…REPLACE</literal> printing duplicate key error when - executing the same load query several times. (Bug #5835) + InnoDB: Fixed a bug in <literal>LOAD DATA INFILE…REPLACE</literal> + printing duplicate key error when executing the same load query + several times. (Bug #5835) </para></listitem> <listitem><para> @@ -31922,6 +31952,16 @@ <itemizedlist> <listitem><para> + OPTIMIZE of InnoDB table does not return 'Table is full' if out of + tablespace. (Bug #8135) + </para></listitem> + + <listitem><para> + GROUP BY queries with ROLLUP returned wrong results for expressions + containing group by columns. (Bug #7894) + </para></listitem> + + <listitem><para> (Bug #11019) mgmapi start backup in some cases returns wrong backupid </para></listitem> @@ -32175,7 +32215,9 @@ <itemizedlist> - <listitem><para>N/A</para></listitem> + <listitem><para> + N/A + </para></listitem> </itemizedlist> @@ -33462,7 +33504,9 @@ <itemizedlist> - <listitem><para>N/A</para></listitem> + <listitem><para> + N/A + </para></listitem> </itemizedlist> --- 1.7/refman-5.0/news.xml 2005-06-21 11:17:31 -06:00 +++ 1.8/refman-5.0/news.xml 2005-06-21 18:22:43 -06:00 @@ -225,22 +225,22 @@ Functionality added or changed: </para> - <itemizedlist> + <itemizedlist> - <listitem> - <para>New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal> - Prevents automatic substitution of storage engine when the requested - storage engine is disabled or not compiled in. (Bug #6877)</para> - </listitem> - - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit.</para> - </listitem> + <listitem><para> + New <literal>SQL_MODE</literal> - + <literal>NO_ENGINE_SUBSTITUTION</literal> Prevents automatic + substitution of storage engine when the requested storage engine is + disabled or not compiled in. (Bug #6877) + </para></listitem> - </itemizedlist> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. + </para></listitem> + + </itemizedlist> <para> Bugs fixed: @@ -248,49 +248,57 @@ <itemizedlist> - <listitem> - <para>An <literal>ORDER BY</literal> clause sometimes had no - effect on the ordering of a result when selecting specific columns - (as opposed to using <literal>SELECT *</literal>) from a view. - (Bug#7422)</para> - </listitem> - - <listitem> - <para>Some data definition statements (<literal>CREATE - TABLE</literal> where the table was not a temporary table, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were - not being written to the binary log after a - <literal>ROLLBACK</literal>. This also caused problems with - replication. (Bug#6883)</para> - </listitem> - - - <listitem> - <para>Calling a stored procedure that made use of an - <literal>INSERT ... SELECT ... UNION SELECT ...</literal> query - caused a server crash. (Bug#11060)</para> - </listitem> - - <listitem> - <para>Selecting from a view defined using <literal>SELECT - SUM(DISTINCT ...)</literal> caused an error; attempting to execute - a <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query - after defining such a view crashed the server. (Bug#7015)</para> - </listitem> - - <listitem> - <para>The <command>mysql</command> client would output a prompt - twice following input of very long strings, because it incorrectly - assumed that a call to the <command>_cgets()</command> function - would clear the input buffer. (Bug#10840) - </para> - </listitem> - - <listitem><para> - A three byte buffer overflow in the client functions caused improper - exiting of the client when reading a command from the user. (Bug - #10841) + <listitem><para> + Fixed hang/crash with Boolean full-text search against an unindexed + field for which the query contained more words than we allocated + space. (Bug #7858) + </para></listitem> + + <listitem><para> + Fixed column name generation in <literal>VIEW</literal> creation to + ensure there are no duplicate column names. (Bug #7448) + </para></listitem> + + <listitem><para> + An <literal>ORDER BY</literal> clause sometimes had no effect on + the ordering of a result when selecting specific columns (as + opposed to using <literal>SELECT *</literal>) from a view. + (Bug#7422) + </para></listitem> + + <listitem><para> + Some data definition statements (<literal>CREATE TABLE</literal> + where the table was not a temporary table, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal>) were not being written to the + binary log after a <literal>ROLLBACK</literal>. This also caused + problems with replication. (Bug#6883) + </para></listitem> + + <listitem><para> + Calling a stored procedure that made use of an <literal>INSERT ... + SELECT ... UNION SELECT ...</literal> query caused a server crash. + (Bug#11060) + </para></listitem> + + <listitem><para> + Selecting from a view defined using <literal>SELECT SUM(DISTINCT + ...)</literal> caused an error; attempting to execute a + <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query + after defining such a view crashed the server. (Bug#7015) + </para></listitem> + + <listitem><para> + The <command>mysql</command> client would output a prompt twice + following input of very long strings, because it incorrectly + assumed that a call to the <command>_cgets()</command> function + would clear the input buffer. (Bug#10840) + </para></listitem> + + <listitem><para> + A three byte buffer overflow in the client functions caused + improper exiting of the client when reading a command from the + user. (Bug #10841) </para></listitem> <listitem><para> @@ -445,14 +453,21 @@ <itemizedlist> -<listitem><para> - Everything you write after the <literal>DELIMITER</literal> keyword will be set as delimiter. Ex: <literal>DELIMITER -:;</literal> will set <literal>:;</literal> as the delimiter. This behavior is now consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) -</para></listitem> - -<listitem><para> - The <literal>table</literal>, <literal>type</literal>, and <literal>rows</literal> columns of <literal>EXPLAIN</literal> output can now be <literal>NULL</literal>. This is required for using <literal>EXPLAIN</literal> on <literal>SELECT</literal> queries that use no tables (i.e. <literal>EXPLAIN SELECT 1</literal>). (Bug #9899) -</para></listitem> + <listitem><para> + Everything you write after the <literal>DELIMITER</literal> keyword + will be set as delimiter. Ex: <literal>DELIMITER :;</literal> will + set <literal>:;</literal> as the delimiter. This behavior is now + consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) + </para></listitem> + + <listitem><para> + The <literal>table</literal>, <literal>type</literal>, and + <literal>rows</literal> columns of <literal>EXPLAIN</literal> + output can now be <literal>NULL</literal>. This is required for + using <literal>EXPLAIN</literal> on <literal>SELECT</literal> + queries that use no tables (i.e. <literal>EXPLAIN SELECT + 1</literal>). (Bug #9899) + </para></listitem> <listitem><para> Placeholders now can be used for <literal>LIMIT</literal> in @@ -512,9 +527,10 @@ <itemizedlist> -<listitem><para> - Fixed bug in <literal>FIELD()</literal> function where value list contains <literal>NULL</literal>. (Bug #10944) -</para></listitem> + <listitem><para> + Fixed bug in <literal>FIELD()</literal> function where value list + contains <literal>NULL</literal>. (Bug #10944) + </para></listitem> <listitem><para> Corrected a problem where an incorrect column type was returned in @@ -2358,8 +2374,8 @@ </para></listitem> <listitem><para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table + InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, single + table <literal>UPDATE…SELECT</literal> and single table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. @@ -4178,14 +4194,14 @@ file. </para></listitem> - <listitem> - <para>The <literal>table</literal>, <literal>type</literal>, and - <literal>rows</literal> columns of <literal>EXPLAIN</literal> - output can now be <literal>NULL</literal>. This is required for - using <literal>EXPLAIN</literal> on <literal>SELECT</literal> - queries that use no tables, such as - <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)</para> - </listitem> + <listitem><para> + The <literal>table</literal>, <literal>type</literal>, and + <literal>rows</literal> columns of <literal>EXPLAIN</literal> + output can now be <literal>NULL</literal>. This is required for + using <literal>EXPLAIN</literal> on <literal>SELECT</literal> + queries that use no tables, such as <literal>EXPLAIN SELECT + 1</literal>). (Bug #9899) + </para></listitem> </itemizedlist> @@ -4198,23 +4214,39 @@ <!-- NOTE: No need to start every item with "Fixed..."; sufficient to describe the issue that was fixed. --> - <listitem> - <para>The <command>mysql</command> client would output a prompt - twice following input of very long strings, because it incorrectly - assumed that a call to the <command>_cgets()</command> function - would clear the input buffer. (Bug#10840)</para> - </listitem> - - <listitem> - <para>A bug in <literal>FIELD()</literal> function caused the value - list to contain <literal>NULL</literal>. (Bug #10944)</para> - </listitem> - - <listitem> - <para>A three byte buffer overflow in the client functions could - cause improper exiting of the client when reading a command from - the user. (Bug #10841)</para> - </listitem> + <listitem><para> + OPTIMIZE of InnoDB table does not return 'Table is full' if out of + tablespace. (Bug #8135) + </para></listitem> + + <listitem><para> + GROUP BY queries with ROLLUP returned wrong results for expressions + containing group by columns. (Bug #7894) + </para></listitem> + + <listitem><para> + Fixed hang/crash with Boolean full-text search against an unindexed + field for which the query contained more words than we allocated + space. (Bug #7858) + </para></listitem> + + <listitem><para> + The <command>mysql</command> client would output a prompt twice + following input of very long strings, because it incorrectly + assumed that a call to the <command>_cgets()</command> function + would clear the input buffer. (Bug#10840) + </para></listitem> + + <listitem><para> + A bug in <literal>FIELD()</literal> function caused the value list + to contain <literal>NULL</literal>. (Bug #10944) + </para></listitem> + + <listitem><para> + A three byte buffer overflow in the client functions could cause + improper exiting of the client when reading a command from the + user. (Bug #10841) + </para></listitem> <listitem><para> Fixed a problem with the <literal>cp1250_czech_cs</literal> @@ -4496,9 +4528,9 @@ isolation level of the transaction is not set to serializable then <literal>InnoDB</literal> uses a consistent read for select in clauses like <literal>INSERT INTO…SELECT</literal> and - <literal>UPDATE…(SELECT)</literal> that do not specify - <literal>FOR UPDATE</literal> or <literal>IN SHARE MODE</literal>. - Thus no locks are set to rows read from selected table. + <literal>UPDATE…(SELECT)</literal> that do not specify <literal>FOR + UPDATE</literal> or <literal>IN SHARE MODE</literal>. Thus no locks + are set to rows read from selected table. </para></listitem> <listitem><para> @@ -5335,8 +5367,8 @@ <listitem><para> A join on two tables failed when each contained a <literal>BIGINT UNSIGNED</literal> column that were compared when their values - exceeded 2^63 - 1. The match failed and the join returned no - rows. (Bug #8562) + exceeded 2^63 - 1. The match failed and the join returned no rows. + (Bug #8562) </para></listitem> <listitem><para> @@ -5839,8 +5871,8 @@ </para></listitem> <listitem><para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table + InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, single + table <literal>UPDATE…SELECT</literal> and single table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. @@ -6647,12 +6679,11 @@ queries; unless <literal>--short-form</literal> is used. </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit.</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. + </para></listitem> </itemizedlist> @@ -6662,15 +6693,14 @@ <itemizedlist> - <listitem> - <para>Some data definition statements (<literal>CREATE - TABLE</literal> where the table was not a temporary table, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were - not being written to the binary log after a - <literal>ROLLBACK</literal>. This also caused problems with - replication. (Bug#6883)</para> - </listitem> + <listitem><para> + Some data definition statements (<literal>CREATE TABLE</literal> + where the table was not a temporary table, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal>) were not being written to the + binary log after a <literal>ROLLBACK</literal>. This also caused + problems with replication. (Bug#6883) + </para></listitem> <listitem><para> Fixed incorrect referencing to column by name from subquery to @@ -7094,9 +7124,9 @@ </para></listitem> <listitem><para> - InnoDB: Fixed a bug in <literal>LOAD DATA - INFILE…REPLACE</literal> printing duplicate key error when - executing the same load query several times. (Bug #5835) + InnoDB: Fixed a bug in <literal>LOAD DATA INFILE…REPLACE</literal> + printing duplicate key error when executing the same load query + several times. (Bug #5835) </para></listitem> <listitem><para> @@ -11014,9 +11044,9 @@ </para></listitem> <listitem><para> - InnoDB: Fixed a bug in <literal>LOAD DATA - INFILE…REPLACE</literal> printing duplicate key error when - executing the same load query several times. (Bug #5835) + InnoDB: Fixed a bug in <literal>LOAD DATA INFILE…REPLACE</literal> + printing duplicate key error when executing the same load query + several times. (Bug #5835) </para></listitem> <listitem><para> @@ -31922,6 +31952,16 @@ <itemizedlist> <listitem><para> + OPTIMIZE of InnoDB table does not return 'Table is full' if out of + tablespace. (Bug #8135) + </para></listitem> + + <listitem><para> + GROUP BY queries with ROLLUP returned wrong results for expressions + containing group by columns. (Bug #7894) + </para></listitem> + + <listitem><para> (Bug #11019) mgmapi start backup in some cases returns wrong backupid </para></listitem> @@ -32175,7 +32215,9 @@ <itemizedlist> - <listitem><para>N/A</para></listitem> + <listitem><para> + N/A + </para></listitem> </itemizedlist> @@ -33462,7 +33504,9 @@ <itemizedlist> - <listitem><para>N/A</para></listitem> + <listitem><para> + N/A + </para></listitem> </itemizedlist> --- 1.11/refman/news.xml 2005-06-21 11:17:32 -06:00 +++ 1.12/refman/news.xml 2005-06-21 18:22:43 -06:00 @@ -225,22 +225,22 @@ Functionality added or changed: </para> - <itemizedlist> + <itemizedlist> - <listitem> - <para>New <literal>SQL_MODE</literal> - <literal>NO_ENGINE_SUBSTITUTION</literal> - Prevents automatic substitution of storage engine when the requested - storage engine is disabled or not compiled in. (Bug #6877)</para> - </listitem> - - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit.</para> - </listitem> + <listitem><para> + New <literal>SQL_MODE</literal> - + <literal>NO_ENGINE_SUBSTITUTION</literal> Prevents automatic + substitution of storage engine when the requested storage engine is + disabled or not compiled in. (Bug #6877) + </para></listitem> - </itemizedlist> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. + </para></listitem> + + </itemizedlist> <para> Bugs fixed: @@ -248,49 +248,57 @@ <itemizedlist> - <listitem> - <para>An <literal>ORDER BY</literal> clause sometimes had no - effect on the ordering of a result when selecting specific columns - (as opposed to using <literal>SELECT *</literal>) from a view. - (Bug#7422)</para> - </listitem> - - <listitem> - <para>Some data definition statements (<literal>CREATE - TABLE</literal> where the table was not a temporary table, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were - not being written to the binary log after a - <literal>ROLLBACK</literal>. This also caused problems with - replication. (Bug#6883)</para> - </listitem> - - - <listitem> - <para>Calling a stored procedure that made use of an - <literal>INSERT ... SELECT ... UNION SELECT ...</literal> query - caused a server crash. (Bug#11060)</para> - </listitem> - - <listitem> - <para>Selecting from a view defined using <literal>SELECT - SUM(DISTINCT ...)</literal> caused an error; attempting to execute - a <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query - after defining such a view crashed the server. (Bug#7015)</para> - </listitem> - - <listitem> - <para>The <command>mysql</command> client would output a prompt - twice following input of very long strings, because it incorrectly - assumed that a call to the <command>_cgets()</command> function - would clear the input buffer. (Bug#10840) - </para> - </listitem> - - <listitem><para> - A three byte buffer overflow in the client functions caused improper - exiting of the client when reading a command from the user. (Bug - #10841) + <listitem><para> + Fixed hang/crash with Boolean full-text search against an unindexed + field for which the query contained more words than we allocated + space. (Bug #7858) + </para></listitem> + + <listitem><para> + Fixed column name generation in <literal>VIEW</literal> creation to + ensure there are no duplicate column names. (Bug #7448) + </para></listitem> + + <listitem><para> + An <literal>ORDER BY</literal> clause sometimes had no effect on + the ordering of a result when selecting specific columns (as + opposed to using <literal>SELECT *</literal>) from a view. + (Bug#7422) + </para></listitem> + + <listitem><para> + Some data definition statements (<literal>CREATE TABLE</literal> + where the table was not a temporary table, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal>) were not being written to the + binary log after a <literal>ROLLBACK</literal>. This also caused + problems with replication. (Bug#6883) + </para></listitem> + + <listitem><para> + Calling a stored procedure that made use of an <literal>INSERT ... + SELECT ... UNION SELECT ...</literal> query caused a server crash. + (Bug#11060) + </para></listitem> + + <listitem><para> + Selecting from a view defined using <literal>SELECT SUM(DISTINCT + ...)</literal> caused an error; attempting to execute a + <literal>SELECT * FROM INFORMATION_SCHEMA.TABLES</literal> query + after defining such a view crashed the server. (Bug#7015) + </para></listitem> + + <listitem><para> + The <command>mysql</command> client would output a prompt twice + following input of very long strings, because it incorrectly + assumed that a call to the <command>_cgets()</command> function + would clear the input buffer. (Bug#10840) + </para></listitem> + + <listitem><para> + A three byte buffer overflow in the client functions caused + improper exiting of the client when reading a command from the + user. (Bug #10841) </para></listitem> <listitem><para> @@ -445,14 +453,21 @@ <itemizedlist> -<listitem><para> - Everything you write after the <literal>DELIMITER</literal> keyword will be set as delimiter. Ex: <literal>DELIMITER -:;</literal> will set <literal>:;</literal> as the delimiter. This behavior is now consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) -</para></listitem> - -<listitem><para> - The <literal>table</literal>, <literal>type</literal>, and <literal>rows</literal> columns of <literal>EXPLAIN</literal> output can now be <literal>NULL</literal>. This is required for using <literal>EXPLAIN</literal> on <literal>SELECT</literal> queries that use no tables (i.e. <literal>EXPLAIN SELECT 1</literal>). (Bug #9899) -</para></listitem> + <listitem><para> + Everything you write after the <literal>DELIMITER</literal> keyword + will be set as delimiter. Ex: <literal>DELIMITER :;</literal> will + set <literal>:;</literal> as the delimiter. This behavior is now + consistent between MySQL 5.1 and MySQL 5.0. (Bug #9879) + </para></listitem> + + <listitem><para> + The <literal>table</literal>, <literal>type</literal>, and + <literal>rows</literal> columns of <literal>EXPLAIN</literal> + output can now be <literal>NULL</literal>. This is required for + using <literal>EXPLAIN</literal> on <literal>SELECT</literal> + queries that use no tables (i.e. <literal>EXPLAIN SELECT + 1</literal>). (Bug #9899) + </para></listitem> <listitem><para> Placeholders now can be used for <literal>LIMIT</literal> in @@ -512,9 +527,10 @@ <itemizedlist> -<listitem><para> - Fixed bug in <literal>FIELD()</literal> function where value list contains <literal>NULL</literal>. (Bug #10944) -</para></listitem> + <listitem><para> + Fixed bug in <literal>FIELD()</literal> function where value list + contains <literal>NULL</literal>. (Bug #10944) + </para></listitem> <listitem><para> Corrected a problem where an incorrect column type was returned in @@ -2358,8 +2374,8 @@ </para></listitem> <listitem><para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table + InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, single + table <literal>UPDATE…SELECT</literal> and single table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. @@ -4178,14 +4194,14 @@ file. </para></listitem> - <listitem> - <para>The <literal>table</literal>, <literal>type</literal>, and - <literal>rows</literal> columns of <literal>EXPLAIN</literal> - output can now be <literal>NULL</literal>. This is required for - using <literal>EXPLAIN</literal> on <literal>SELECT</literal> - queries that use no tables, such as - <literal>EXPLAIN SELECT 1</literal>). (Bug #9899)</para> - </listitem> + <listitem><para> + The <literal>table</literal>, <literal>type</literal>, and + <literal>rows</literal> columns of <literal>EXPLAIN</literal> + output can now be <literal>NULL</literal>. This is required for + using <literal>EXPLAIN</literal> on <literal>SELECT</literal> + queries that use no tables, such as <literal>EXPLAIN SELECT + 1</literal>). (Bug #9899) + </para></listitem> </itemizedlist> @@ -4198,23 +4214,39 @@ <!-- NOTE: No need to start every item with "Fixed..."; sufficient to describe the issue that was fixed. --> - <listitem> - <para>The <command>mysql</command> client would output a prompt - twice following input of very long strings, because it incorrectly - assumed that a call to the <command>_cgets()</command> function - would clear the input buffer. (Bug#10840)</para> - </listitem> - - <listitem> - <para>A bug in <literal>FIELD()</literal> function caused the value - list to contain <literal>NULL</literal>. (Bug #10944)</para> - </listitem> - - <listitem> - <para>A three byte buffer overflow in the client functions could - cause improper exiting of the client when reading a command from - the user. (Bug #10841)</para> - </listitem> + <listitem><para> + OPTIMIZE of InnoDB table does not return 'Table is full' if out of + tablespace. (Bug #8135) + </para></listitem> + + <listitem><para> + GROUP BY queries with ROLLUP returned wrong results for expressions + containing group by columns. (Bug #7894) + </para></listitem> + + <listitem><para> + Fixed hang/crash with Boolean full-text search against an unindexed + field for which the query contained more words than we allocated + space. (Bug #7858) + </para></listitem> + + <listitem><para> + The <command>mysql</command> client would output a prompt twice + following input of very long strings, because it incorrectly + assumed that a call to the <command>_cgets()</command> function + would clear the input buffer. (Bug#10840) + </para></listitem> + + <listitem><para> + A bug in <literal>FIELD()</literal> function caused the value list + to contain <literal>NULL</literal>. (Bug #10944) + </para></listitem> + + <listitem><para> + A three byte buffer overflow in the client functions could cause + improper exiting of the client when reading a command from the + user. (Bug #10841) + </para></listitem> <listitem><para> Fixed a problem with the <literal>cp1250_czech_cs</literal> @@ -4496,9 +4528,9 @@ isolation level of the transaction is not set to serializable then <literal>InnoDB</literal> uses a consistent read for select in clauses like <literal>INSERT INTO…SELECT</literal> and - <literal>UPDATE…(SELECT)</literal> that do not specify - <literal>FOR UPDATE</literal> or <literal>IN SHARE MODE</literal>. - Thus no locks are set to rows read from selected table. + <literal>UPDATE…(SELECT)</literal> that do not specify <literal>FOR + UPDATE</literal> or <literal>IN SHARE MODE</literal>. Thus no locks + are set to rows read from selected table. </para></listitem> <listitem><para> @@ -5335,8 +5367,8 @@ <listitem><para> A join on two tables failed when each contained a <literal>BIGINT UNSIGNED</literal> column that were compared when their values - exceeded 2^63 - 1. The match failed and the join returned no - rows. (Bug #8562) + exceeded 2^63 - 1. The match failed and the join returned no rows. + (Bug #8562) </para></listitem> <listitem><para> @@ -5839,8 +5871,8 @@ </para></listitem> <listitem><para> - InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, - single table <literal>UPDATE…SELECT</literal> and single table + InnoDB: Relaxed locking in <literal>INSERT…SELECT</literal>, single + table <literal>UPDATE…SELECT</literal> and single table <literal>DELETE…SELECT</literal> clauses when <literal>innodb_locks_unsafe_for_binlog</literal> is used and isolation level of the transaction is not serializable. @@ -6647,12 +6679,11 @@ queries; unless <literal>--short-form</literal> is used. </para></listitem> - <listitem> - <para>The statements <literal>CREATE TABLE</literal>, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal> cause - an implicit commit.</para> - </listitem> + <listitem><para> + The statements <literal>CREATE TABLE</literal>, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal> cause an implicit commit. + </para></listitem> </itemizedlist> @@ -6662,15 +6693,14 @@ <itemizedlist> - <listitem> - <para>Some data definition statements (<literal>CREATE - TABLE</literal> where the table was not a temporary table, - <literal>TRUNCATE TABLE</literal>, <literal>DROP - DATABASE</literal>, and <literal>CREATE DATABASE</literal>) were - not being written to the binary log after a - <literal>ROLLBACK</literal>. This also caused problems with - replication. (Bug#6883)</para> - </listitem> + <listitem><para> + Some data definition statements (<literal>CREATE TABLE</literal> + where the table was not a temporary table, <literal>TRUNCATE + TABLE</literal>, <literal>DROP DATABASE</literal>, and + <literal>CREATE DATABASE</literal>) were not being written to the + binary log after a <literal>ROLLBACK</literal>. This also caused + problems with replication. (Bug#6883) + </para></listitem> <listitem><para> Fixed incorrect referencing to column by name from subquery to @@ -7094,9 +7124,9 @@ </para></listitem> <listitem><para> - InnoDB: Fixed a bug in <literal>LOAD DATA - INFILE…REPLACE</literal> printing duplicate key error when - executing the same load query several times. (Bug #5835) + InnoDB: Fixed a bug in <literal>LOAD DATA INFILE…REPLACE</literal> + printing duplicate key error when executing the same load query + several times. (Bug #5835) </para></listitem> <listitem><para> @@ -11014,9 +11044,9 @@ </para></listitem> <listitem><para> - InnoDB: Fixed a bug in <literal>LOAD DATA - INFILE…REPLACE</literal> printing duplicate key error when - executing the same load query several times. (Bug #5835) + InnoDB: Fixed a bug in <literal>LOAD DATA INFILE…REPLACE</literal> + printing duplicate key error when executing the same load query + several times. (Bug #5835) </para></listitem> <listitem><para> @@ -31922,6 +31952,16 @@ <itemizedlist> <listitem><para> + OPTIMIZE of InnoDB table does not return 'Table is full' if out of + tablespace. (Bug #8135) + </para></listitem> + + <listitem><para> + GROUP BY queries with ROLLUP returned wrong results for expressions + containing group by columns. (Bug #7894) + </para></listitem> + + <listitem><para> (Bug #11019) mgmapi start backup in some cases returns wrong backupid </para></listitem> @@ -32175,7 +32215,9 @@ <itemizedlist> - <listitem><para>N/A</para></listitem> + <listitem><para> + N/A + </para></listitem> </itemizedlist> @@ -33462,7 +33504,9 @@ <itemizedlist> - <listitem><para>N/A</para></listitem> + <listitem><para> + N/A + </para></listitem> </itemizedlist>
| Thread | ||
|---|---|---|
| • bk commit - mysqldoc@docsrva tree (Mike.Hillyer:1.2848) | mhillyer | 22 Jun |
© 1995-2008 MySQL AB, 2008-2009 Sun Microsystems, Inc.
Page generated in 0.931 sec. using MySQL 5.1.14-beta-log