| List: | Commits | « Previous MessageNext Message » | |
| From: | paul | Date: | November 19 2007 6:42am |
| Subject: | svn commit - mysqldoc@docsrva: r8785 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-6.0 | ||
| View as plain text | |||
Author: paul Date: 2007-11-19 06:42:20 +0100 (Mon, 19 Nov 2007) New Revision: 8785 Log: r27196@frost: paul | 2007-11-18 23:40:19 -0600 Document bugfixes: Bug#25421: MySQL threads don't respond to the kill command Bug#28076: inconsistent binary/varbinary comparison Bug#30329: main.information_schema_chmod test Bug#30666: Incorrect order when using range conditions on 2 tables or more Bug#30715: Assertion failed: item_field->field->real_maybe_null(), file .\opt_sum.cc, line Bug#30897: GROUP_CONCAT returns extra comma on empty fields Bug#31036: Using order by with archive table crashes server Bug#31113: mysqldump 5.1 can't handle a dash ("-") in database names Bug#31159: fulltext search on ucs2 column crashes server Bug#31630: debug assert with explain extended select ... from i_s Bug#31866: MySQL Server crashes on SHOW CREATE TRIGGER statement Bug#32103: optimizer crash when join on int and mediumint with variable in where clause.. Bug#32202: ORDER BY not working with GROUP BY Bug#32229: optimizer crash ... Bug#32262: crash with decimal column... Modified: trunk/dynamic-docs/changelog/mysqld.xml trunk/refman-4.1/functions-core.xml trunk/refman-5.0/functions-core.xml trunk/refman-5.1/functions-core.xml trunk/refman-6.0/functions-core.xml Property changes on: trunk ___________________________________________________________________ Name: svk:merge - 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:32927 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:27195 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22282 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:32927 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:27196 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:22282 Modified: trunk/dynamic-docs/changelog/mysqld.xml =================================================================== --- trunk/dynamic-docs/changelog/mysqld.xml 2007-11-19 05:42:06 UTC (rev 8784) +++ trunk/dynamic-docs/changelog/mysqld.xml 2007-11-19 05:42:20 UTC (rev 8785) Changed blocks: 1, Lines Added: 413, Lines Deleted: 0; 7799 bytes @@ -140003,4 +140003,417 @@ </logentry> + <logentry entrytype="bug"> + + <tags> + <manual type="EXPLAIN"/> + <manual type="INFORMATION_SCHEMA"/> + </tags> + + <bugs> + <fixes bugid="31630"/> + </bugs> + + <versions> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + <literal>EXPLAIN EXTENDED</literal> for + <literal>SELECT</literal> from + <literal>INFORMATION_SCHEMA</literal> tables caused an assertion + failure. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="SHOW CREATE TRIGGER"/> + <manual type="triggers"/> + </tags> + + <bugs> + <fixes bugid="31866"/> + </bugs> + + <versions> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + <literal>SHOW CREATE TRIGGER</literal> caused a server crash. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="ARCHIVE"/> + <manual type="ORDER BY"/> + </tags> + + <bugs> + <fixes bugid="31036"/> + </bugs> + + <versions> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + Using <literal>ORDER BY</literal> with + <literal>ARCHIVE</literal> tables caused a server crash. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="mysqldump"/> + </tags> + + <bugs> + <fixes bugid="31113"/> + </bugs> + + <versions> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + <command>mysqldump</command> failed to handle databases + containing a ‘<literal>-</literal>’ character in the + name. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="optimizer"/> + <manual type="ORDER BY"/> + </tags> + + <bugs> + <fixes bugid="30666"/> + </bugs> + + <versions> + <version ver="5.0.52"/> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + The optimizer could ignore <literal>ORDER BY</literal> in cases + when the result set is ordered by <literal>filesort</literal>, + resulting in rows being returned in incorrect order. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="GROUP_CONCAT()"/> + </tags> + + <bugs> + <fixes bugid="30897"/> + </bugs> + + <versions> + <version ver="5.0.52"/> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + <function role="sql">GROUP_CONCAT()</function> returned + <literal>','</literal> rather than an empty string when the + argument column contained only empty strings. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="optimizer"/> + </tags> + + <bugs> + <fixes bugid="30715"/> + </bugs> + + <versions> + <version ver="5.0.52"/> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + Using the <function role="sql">MIN()</function> or + <function role="sql">MAX()</function> function to select one + part of a multi-part key could cause a crash when the function + result was <literal>NULL</literal>. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="libmysqld"/> + <manual type="privileges"/> + </tags> + + <bugs> + <fixes bugid="30329"/> + </bugs> + + <versions> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + A table-access check was performed improperly by + <literal>libmysqld</literal>, causing a crash. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="BINARY"/> + <manual type="VARBINARY"/> + </tags> + + <bugs> + <fixes bugid="28076"/> + </bugs> + + <versions> + <version ver="5.0.52"/> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + The result of a comparison between <literal>VARBINARY</literal> + and <literal>BINARY</literal> columns differed depending on + whether the <literal>VARBINARY</literal> column was indexed. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="KILL"/> + </tags> + + <bugs> + <fixes bugid="25421"/> + </bugs> + + <versions> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + Some threads did not respond to the <literal>KILL</literal> + statement. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="optimizer"/> + </tags> + + <bugs> + <fixes bugid="32103"/> + </bugs> + + <versions> + <version ver="4.1.24"/> + <version ver="5.0.52"/> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + The server crashed on optimizations involving a join of + <literal>INT</literal> and <literal>MEDIUMINT</literal> columns + and a system variable in the <literal>WHERE</literal> clause. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="ORDER BY"/> + <manual type="GROUP BY"/> + </tags> + + <bugs> + <fixes bugid="32202"/> + </bugs> + + <versions> + <version ver="5.0.52"/> + <version ver="5.1.23"/> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + Under certain conditions, the presence of a <literal>GROUP + BY</literal> clause could cause an <literal>ORDER BY</literal> + clause to be ignored. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="optimizer"/> + </tags> + + <bugs> + <fixes bugid="32229"/> + </bugs> + + <versions> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + The server crashed on optimizations that used the <literal>range + checked for each record</literal> access method. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="optimizer"/> + </tags> + + <bugs> + <fixes bugid="32262"/> + </bugs> + + <versions> + <version ver="6.0.4"/> + </versions> + + <message> + + <para> + The server crashed on optimization of queries that compared an + indexed <literal>DECIMAL</literal> column with a string value. + </para> + + </message> + + </logentry> + + <logentry entrytype="bug"> + + <tags> + <manual type="full-text"/> + </tags> + + <bugs> + <fixes bugid="31159"/> + </bugs> + + <versions> + <version ver="4.1.24"/> + <version ver="5.0.52"/> + </versions> + + <message> + + <para> + Full-text searches on <literal>ucs2</literal> columns caused a + server crash. (<literal>FULLTEXT</literal> indexes on + <literal>ucs2</literal> columns cannot be used, but it should be + possible to perform <literal>IN BOOLEAN MODE</literal> searches + on <literal>ucs2</literal> columns without a crash.) + </para> + + </message> + + </logentry> + </changelog> Modified: trunk/refman-4.1/functions-core.xml =================================================================== --- trunk/refman-4.1/functions-core.xml 2007-11-19 05:42:06 UTC (rev 8784) +++ trunk/refman-4.1/functions-core.xml 2007-11-19 05:42:20 UTC (rev 8785) Changed blocks: 2, Lines Added: 4, Lines Deleted: 1; 931 bytes @@ -11975,6 +11975,10 @@ multi-byte character sets. The exception is that for Unicode, the <literal>utf8</literal> character set can be used, but not the <literal>ucs2</literal> character set. + However, although <literal>FULLTEXT</literal> indexes on + <literal>ucs2</literal> columns cannot be used, you can + perform <literal>IN BOOLEAN MODE</literal> searches on a + <literal>ucs2</literal> column that has no such index. </para> </listitem> @@ -13189,7 +13193,6 @@ </para> <remark role="help-description-end"/> - </listitem> <listitem> Modified: trunk/refman-5.0/functions-core.xml =================================================================== --- trunk/refman-5.0/functions-core.xml 2007-11-19 05:42:06 UTC (rev 8784) +++ trunk/refman-5.0/functions-core.xml 2007-11-19 05:42:20 UTC (rev 8785) Changed blocks: 2, Lines Added: 5, Lines Deleted: 2; 1039 bytes @@ -12249,7 +12249,11 @@ Full-text searches can be used with most multi-byte character sets. The exception is that for Unicode, the <literal>utf8</literal> character set can be used, but not - the <literal>ucs2</literal> character set. + the <literal>ucs2</literal> character set. However, although + <literal>FULLTEXT</literal> indexes on + <literal>ucs2</literal> columns cannot be used, you can + perform <literal>IN BOOLEAN MODE</literal> searches on a + <literal>ucs2</literal> column that has no such index. </para> </listitem> @@ -13372,7 +13376,6 @@ </para> <remark role="help-description-end"/> - </listitem> <listitem> Modified: trunk/refman-5.1/functions-core.xml =================================================================== --- trunk/refman-5.1/functions-core.xml 2007-11-19 05:42:06 UTC (rev 8784) +++ trunk/refman-5.1/functions-core.xml 2007-11-19 05:42:20 UTC (rev 8785) Changed blocks: 2, Lines Added: 5, Lines Deleted: 2; 1039 bytes @@ -12225,7 +12225,11 @@ Full-text searches can be used with most multi-byte character sets. The exception is that for Unicode, the <literal>utf8</literal> character set can be used, but not - the <literal>ucs2</literal> character set. + the <literal>ucs2</literal> character set. However, although + <literal>FULLTEXT</literal> indexes on + <literal>ucs2</literal> columns cannot be used, you can + perform <literal>IN BOOLEAN MODE</literal> searches on a + <literal>ucs2</literal> column that has no such index. </para> </listitem> @@ -14240,7 +14244,6 @@ </para> <remark role="help-description-end"/> - </listitem> <listitem> Modified: trunk/refman-6.0/functions-core.xml =================================================================== --- trunk/refman-6.0/functions-core.xml 2007-11-19 05:42:06 UTC (rev 8784) +++ trunk/refman-6.0/functions-core.xml 2007-11-19 05:42:20 UTC (rev 8785) Changed blocks: 2, Lines Added: 5, Lines Deleted: 2; 1039 bytes @@ -12206,7 +12206,11 @@ Full-text searches can be used with most multi-byte character sets. The exception is that for Unicode, the <literal>utf8</literal> character set can be used, but not - the <literal>ucs2</literal> character set. + the <literal>ucs2</literal> character set. However, although + <literal>FULLTEXT</literal> indexes on + <literal>ucs2</literal> columns cannot be used, you can + perform <literal>IN BOOLEAN MODE</literal> searches on a + <literal>ucs2</literal> column that has no such index. </para> </listitem> @@ -14168,7 +14172,6 @@ </para> <remark role="help-description-end"/> - </listitem> <listitem>
| Thread | ||
|---|---|---|
| • svn commit - mysqldoc@docsrva: r8785 - in trunk: . dynamic-docs/changelog refman-4.1 refman-5.0 refman-5.1 refman-6.0 | paul | 19 Nov |
© 1995-2008 MySQL AB. All rights reserved.
Page generated in 0.643 sec. using MySQL 5.1.14-beta-log