|
|
| Applications |
| Mailing Lists |
| Miscellaneous |
| Operating Systems |
| Programming |
svn commit - mysqldoc@docsrva: r7294 - in trunk: . refman-5.0 refman-5.1
From: <paul(at)mysql.com>
Date: Tue Jul 31 2007 - 15:21:23 EDT
Name: svk:merge
Date: Tue Jul 31 2007 - 15:21:23 EDT
Author: paul
Date: 2007-07-31 21:20:35 +0200 (Tue, 31 Jul 2007)
New Revision: 7294
Log:
r19144@kite-hub: paul | 2007-07-31 14:05:22 -0500
Document bugfixes:
Bug#25679 Bug#26325 Bug#28838
Modified:
trunk/refman-5.0/releasenotes-es-5.0.xml trunk/refman-5.1/news-5.1.xml
Property changes on: trunk
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:28087 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23143 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:19143 + 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:28087 7d8d2c4e-af1d-0410-ab9f-b038ce55645b:/mysqldoc-local/mysqldoc:23143 b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:14218 bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:19144
Modified: trunk/refman-5.0/releasenotes-es-5.0.xml
- trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-31 19:18:01 UTC (rev 7293) +++ trunk/refman-5.0/releasenotes-es-5.0.xml 2007-07-31 19:20:35 UTC (rev 7294) Changed blocks: 1, Lines Added: 9, Lines Deleted: 353; 13349 bytes
@@ -83,374 +83,30 @@
<listitem>
- NDB Cluster : The output from
- ndb_config
-
- was sent to stdout rather than
- stderr . (Bug #25941)
+ ALTER TABLE acquired duplicate locks under
+ some circumstances. This could result in loss of a data row.
+ (Bug #28838)
</listitem>
<listitem>
- On Mac OS X, shared-library installation pathnames were
- incorrect. (Bug #28544)
+ After the first read of a TEMPORARY table,
+ CHECK TABLE could report the table as being
+ corrupt. (Bug #26325)
</listitem>
<listitem>
- For MyISAM tables on Windows,
- INSERT , DELETE , or
- UPDATE followed by ALTER
- TABLE within LOCK TABLES could
- cause table corruption. (Bug #29957)
+ The server was blocked from opening other tables while the
+ FEDERATED engine was attempting to open a
+ remote table. (Bug #25679)
</listitem>
<listitem>
- When using a FEDERATED table, the value of
- last_insert_id() would not correctly update
- the C API interface, which would affect the autogenerated ID
- returned both through the C API and the MySQL protocol,
- affecting Connectors that used the protocol and/or C API. (Bug
- #25714)
-
-
-
-
-
- Optimization of queries with DETERMINISTIC
- stored functions in the WHERE clause was
- ineffective: A sequential scan was always used. (Bug #29338)
-
-
-
-
-
- SQL_BIG_RESULT had no effect for
- CREATE TABLE ... SELECT SQL_BIG_RESULT ...
- statements. (Bug #15130)
-
-
-
-
-
- For InnoDB tables, MySQL unnecessarily
- sorted records in certain cases when the records were
- retrieved by InnoDB in the proper order
- already. (Bug #28591)
-
-
-
-
-
- EXPLAIN produced Impossible
- where for statements of the form SELECT ...
- FROM t WHERE c=0 , where c was an
- ENUM column defined as a primary key. (Bug
- #29661)
-
-
-
-
-
- On Windows, ALTER TABLE hung if records
- were locked in share mode by a long-running transaction. (Bug
- #29644)
-
-
-
-
-
- A field packet with NULL fields caused a
- libmysqlclient crash. (Bug #29494)
-
-
-
-
-
- A byte-order issue in writing a spatial index to disk caused
- bad index files on some systems. (Bug #29070)
-
-
-
-
-
- mysqldump produced output that incorrectly
- discarded the NO_AUTO_VALUE_ON_ZERO value
- of the SQL_MODE variable after dumping
- triggers. (Bug #29788)
-
-
-
-
-
- A statement of the form CREATE TABLE IF NOT EXISTS t1
- SELECT f1() AS i failed with a deadlock error if the
- stored function f1() referred to a table
- with the same name as the to-be-created table. Now it
- correctly produces a message that the table already exists.
- (Bug #22427)
-
-
-
-
-
- Adding DISTINCT could cause incorrect rows
- to appear in a query result. (Bug #29911)
-
-
-
-
-
- Killing an INSERT DELAYED thread caused a
- server crash. (Bug #29431)
-
-
-
-
-
- The special zero
ENUM value
- was coerced to the normal empty string ENUM
- value during a column-to-column copy. This affected
- CREATE ... SELECT statements and
- SELECT statements with aggregate functions
- on ENUM columns in the GROUP
- BY clause. (Bug #29360)
-
-
-
-
-
- Conversion of ASCII DEL (0x7F ) to Unicode
- incorrectly resulted in QUESTION MARK
- (0x3F ) rather than DEL. (Bug #29499)
-
-
-
-
-
- A left join between two views could produce incorrect results.
- (Bug #29604)
-
-
-
-
-
- For MEMORY tables, the
- index_merge union access method could
- return incorrect results. (Bug #29740)
-
-
-
-
-
- If query execution involved a temporary table,
- GROUP_CONCAT() could return a result with
- an incorrect character set. (Bug #29850)
-
-
-
-
-
- Slave servers could incorrectly interpret an out-of-memory
- error from the master and reconnect using the wrong binary log
- position. (Bug #24192)
-
-
-
-
-
- Comparison of TIME values using the
- BETWEEN operator led to string comparison,
- producing incorrect results in some cases. Now the values are
- compared as integers. (Bug #29739)
-
-
-
-
-
- An incorrect result was returned when comparing string values
- that were converted to TIME values with
- CAST() . (Bug #29555)
-
-
-
-
-
- On Windows, the mysql client died if the
- user entered a statement and Return after entering Control-C.
- (Bug #29469)
-
-
-
-
-
- For the general query log, logging of prepared statements
- executed via the C API differed from logging of prepared
- statements performed with PREPARE and
- EXECUTE . Logging for the latter was missing
- the Prepare and Execute
- lines. (Bug #13326)
-
-
-
-
-
- If an operation had an InnoDB table, and
- two triggers, AFTER UPDATE and
- AFTER INSERT , competing for different
- resources (such as two distinct MyISAM
- tables), the triggers were unable to execute concurrently. In
- addition, INSERT and
- UPDATE statements for the
- InnoDB table were unable to run
- concurrently. (Bug #26141)
-
-
-
-
-
- Using the DATE() function in a
- WHERE clause did not return any records
- after encountering NULL . However, using
- TRIM or CAST produced
- the correct results. (Bug #29898)
-
-
-
-
-
- Using the option with
- mysqldump generated incorrect SQL if the
- database included any views. The recreation of views requires
- the creation and removal of temporary tables. This option
- suppressed the removal of those temporary tables. The same
- applied to since this option also
- invokes . (Bug #28524)
-
-
-
-
-
- A race condition in the interaction between
- MyISAM and the query cache code caused the
- query cache not to invalidate itself for concurrently inserted
- data. (Bug #28249)
-
-
-
-
-
- Failure to consider collation when comparing space characters
- could lead to incorrect index entry order, making it
- impossible to find some index values. (Bug #29461)
-
-
-
-
-
- Several InnoDB assertion failures were
- corrected. (Bug #25645)
-
-
-
-
-
- Backup software can cause
- ERROR_SHARING_VIOLATION or
- ERROR_LOCK_VIOLATION conditions during file
- operations. InnoDB now retries forever
- until the condition goes away. (Bug #9709)
-
-
-
-
-
- MyISAM corruption could occur with the
- cp932_japanese_ci collation for the
- cp932 character set due to incorrect
- comparison for trailing space. (Bug #29333)
-
-
-
-
-
- Clients using SSL could hang the server. (Bug #29579)
-
-
-
-
-
- For a table with a DATE column
- date_col such that selecting rows
- with WHERE date_col =
- 'date_val 00:00:00'
- yielded a non-empty result, adding GROUP BY
- date_col caused the
- result to be empty. (Bug #29729)
-
-
-
-
-
- If a stored procedure was created and invoked prior to
- selecting a default database with USE , a
- No database selected error occurred.
- (Bug #28551)
-
-
-
-
-
- Indexing column prefixes in InnoDB tables
- could cause table corruption. (Bug #28138)
-
-
-
-
-
- INSERT INTO ... SELECT caused a crash if
- innodb_locks_unsafe_for_binlog was enabled.
- (Bug #27294)
-
-
-
-
-
- SHOW INNODB STATUS caused an assertion
- failure under high load. (Bug #22819)
-
-
-
-
-
- On Windows, the server used 10MB of memory for each connection
- thread, resulting in memory exhaustion. Now each thread uses
- 1MB. (Bug #20815)
-
-
-
-
-
- For the embedded server, the
- mysql_stmt_store_result() C API function
- caused a memory leak for empty result sets. (Bug #29687)
-
-
-
-
-
- mysql-stress-test.pl and
- mysqld_multi.server.sh were missing from
- some binary distributions. (Bug #21023, Bug #25486)
-
-
-
-
-
ALTER DATABASE did not require at least one
option. (Bug #25859)
Modified: trunk/refman-5.1/news-5.1.xml
- trunk/refman-5.1/news-5.1.xml 2007-07-31 19:18:01 UTC (rev 7293) +++ trunk/refman-5.1/news-5.1.xml 2007-07-31 19:20:35 UTC (rev 7294) Changed blocks: 1, Lines Added: 9, Lines Deleted: 451; 16790 bytes
@@ -248,472 +248,30 @@
<listitem>
- On Mac OS X, shared-library installation pathnames were
- incorrect. (Bug #28544)
+ ALTER TABLE acquired duplicate locks under
+ some circumstances. This could result in loss of a data row.
+ (Bug #28838)
</listitem>
<listitem>
- For MyISAM tables on Windows,
- INSERT , DELETE , or
- UPDATE followed by ALTER
- TABLE within LOCK TABLES could
- cause table corruption. (Bug #29957)
+ After the first read of a TEMPORARY table,
+ CHECK TABLE could report the table as being
+ corrupt. (Bug #26325)
</listitem>
<listitem>
- When determining which transaction to kill after deadlock has
- been detected, InnoDB now adds the number
- of locks to a transaction's weight, and avoids killing
- transactions that mave modified non-transactional tables. This
- should reduce the likelihood of killing long-running
- transactions containing SELECT ... FOR
- UPDATE or INSERT/REPLACE INTO ...
- SELECT statements, and of causing partial updates if
- the target is a MyISAM table. (Bug #21293)
+ The server was blocked from opening other tables while the
+ FEDERATED engine was attempting to open a
+ remote table. (Bug #25679)
</listitem>
<listitem>
- When using a FEDERATED table, the value of
- last_insert_id() would not correctly update
- the C API interface, which would affect the autogenerated ID
- returned both through the C API and the MySQL protocol,
- affecting Connectors that used the protocol and/or C API. (Bug
- #25714)
-
-
-
-
-
- Optimization of queries with DETERMINISTIC
- stored functions in the WHERE clause was
- ineffective: A sequential scan was always used. (Bug #29338)
-
-
-
-
-
- SQL_BIG_RESULT had no effect for
- CREATE TABLE ... SELECT SQL_BIG_RESULT ...
- statements. (Bug #15130)
-
-
-
-
-
- For InnoDB tables, MySQL unnecessarily
- sorted records in certain cases when the records were
- retrieved by InnoDB in the proper order
- already. (Bug #28591)
-
-
-
-
-
- EXPLAIN produced Impossible
- where for statements of the form SELECT ...
- FROM t WHERE c=0 , where c was an
- ENUM column defined as a primary key. (Bug
- #29661)
-
-
-
-
-
- On Windows, ALTER TABLE hung if records
- were locked in share mode by a long-running transaction. (Bug
- #29644)
-
-
-
-
-
- A field packet with NULL fields caused a
- libmysqlclient crash. (Bug #29494)
-
-
-
-
-
- A byte-order issue in writing a spatial index to disk caused
- bad index files on some systems. (Bug #29070)
-
-
-
-
-
- mysqldump produced output that incorrectly
- discarded the NO_AUTO_VALUE_ON_ZERO value
- of the SQL_MODE variable after dumping
- triggers. (Bug #29788)
-
-
-
-
-
- A statement of the form CREATE TABLE IF NOT EXISTS t1
- SELECT f1() AS i failed with a deadlock error if the
- stored function f1() referred to a table
- with the same name as the to-be-created table. Now it
- correctly produces a message that the table already exists.
- (Bug #22427)
-
-
-
-
-
- Adding DISTINCT could cause incorrect rows
- to appear in a query result. (Bug #29911)
-
-
-
-
-
- Killing an INSERT DELAYED thread caused a
- server crash. (Bug #29431)
-
-
-
-
-
- For updates to InnoDB tables, a
- TIMESTAMP column with the ON
- UPDATE CURRENT_TIMESTAMP attribute could be updated
- even when no values actually changed. (Bug #29310)
-
-
-
-
-
- The special zero
ENUM value
- was coerced to the normal empty string ENUM
- value during a column-to-column copy. This affected
- CREATE ... SELECT statements and
- SELECT statements with aggregate functions
- on ENUM columns in the GROUP
- BY clause. (Bug #29360)
-
-
-
-
-
- Conversion of ASCII DEL (0x7F ) to Unicode
- incorrectly resulted in QUESTION MARK
- (0x3F ) rather than DEL. (Bug #29499)
-
-
-
-
-
- A left join between two views could produce incorrect results.
- (Bug #29604)
-
-
-
-
-
- For MEMORY tables, the
- index_merge union access method could
- return incorrect results. (Bug #29740)
-
-
-
-
-
- If query execution involved a temporary table,
- GROUP_CONCAT() could return a result with
- an incorrect character set. (Bug #29850)
-
-
-
-
-
- Slave servers could incorrectly interpret an out-of-memory
- error from the master and reconnect using the wrong binary log
- position. (Bug #24192)
-
-
-
-
-
- Comparison of TIME values using the
- BETWEEN operator led to string comparison,
- producing incorrect results in some cases. Now the values are
- compared as integers. (Bug #29739)
-
-
-
-
-
- An incorrect result was returned when comparing string values
- that were converted to TIME values with
- CAST() . (Bug #29555)
-
-
-
-
-
- If InnoDB reached its limit on the number
- of concurrent transactions (1023), it wrote a descriptive
- message to the error log but returned a misleading error
- message to the client, or an assertion failure occurred. (Bug
- #18828)
-
-
-
-
-
- On Windows, the mysql client died if the
- user entered a statement and Return after entering Control-C.
- (Bug #29469)
-
-
-
-
-
- For the general query log, logging of prepared statements
- executed via the C API differed from logging of prepared
- statements performed with PREPARE and
- EXECUTE . Logging for the latter was missing
- the Prepare and Execute
- lines. (Bug #13326)
-
-
-
-
-
- Under heavy load with a large query cache, invalidating part
- of the cache could cause the server to freeze (that is, to be
- unable to service other operations until the invalidation was
- complete). (Bug #21074)
-
-
-
-
-
- If an operation had an InnoDB table, and
- two triggers, AFTER UPDATE and
- AFTER INSERT , competing for different
- resources (such as two distinct MyISAM
- tables), the triggers were unable to execute concurrently. In
- addition, INSERT and
- UPDATE statements for the
- InnoDB table were unable to run
- concurrently. (Bug #26141)
-
-
-
-
-
- On 64-bit platforms, the filesort code (for queries with
- GROUP BY or ORDER BY )
- could crash due to an incorrect pointer size. (Bug #29610)
-
-
-
-
-
- Using the DATE() function in a
- WHERE clause did not return any records
- after encountering NULL . However, using
- TRIM or CAST produced
- the correct results. (Bug #29898)
-
-
-
-
-
- Using the option with
- mysqldump generated incorrect SQL if the
- database included any views. The recreation of views requires
- the creation and removal of temporary tables. This option
- suppressed the removal of those temporary tables. The same
- applied to since this option also
- invokes . (Bug #28524)
-
-
-
-
-
- A race condition in the interaction between
- MyISAM and the query cache code caused the
- query cache not to invalidate itself for concurrently inserted
- data. (Bug #28249)
-
-
-
-
-
- The full-text parser could enter an infinite loop if it
- encountered an illegal multi-byte sequence or a sequence that
- has no mapping to Unicode. (Bug #29464)
-
-
-
-
-
- Failure to consider collation when comparing space characters
- could lead to incorrect index entry order, making it
- impossible to find some index values. (Bug #29461)
-
-
-
-
-
- Several InnoDB assertion failures were
- corrected. (Bug #25645)
-
-
-
-
-
- InnoDB displayed an incorrect error message
- when a CREATE TABLE statement exceeded the
- InnoDB maximum allowable row size. (Bug
- #21101)
-
-
-
-
-
- InnoDB produced an unnecessary (and
- harmless) warning: InnoDB: Error: trying to declare
- trx to enter InnoDB, but InnoDB: it already is
- declared . (Bug #20090)
-
-
-
-
-
- Backup software can cause
- ERROR_SHARING_VIOLATION or
- ERROR_LOCK_VIOLATION conditions during file
- operations. InnoDB now retries forever
- until the condition goes away. (Bug #9709)
-
-
-
-
-
- In strict SQL mode, errors silently stopped the SQL thread
- even for errors named using the
- option. (Bug #28839)
-
-
-
-
-
- MyISAM corruption could occur with the
- cp932_japanese_ci collation for the
- cp932 character set due to incorrect
- comparison for trailing space. (Bug #29333)
-
-
-
-
-
- Searching a FULLTEXT index for a word with
- the boolean mode truncation operator could cause an infinite
- loop. (Bug #29445)
-
-
-
-
-
- CHECK TABLE could erroneously report table
- corruption for a CSV table if multiple
- threads were modifying the table at the same time. (Bug
- #29253)
-
-
-
-
-
- Clients using SSL could hang the server. (Bug #29579)
-
-
-
-
-
- Single-row inserts could report a row count greater than one.
- (Bug #29692)
-
-
-
-
-
- For a table with a DATE column
- date_col such that selecting rows
- with WHERE date_col =
- 'date_val 00:00:00'
- yielded a non-empty result, adding GROUP BY
- date_col caused the
- result to be empty. (Bug #29729)
-
-
-
-
-
- If a stored procedure was created and invoked prior to
- selecting a default database with USE , a
- No database selected error occurred.
- (Bug #28551)
-
-
-
-
-
- Indexing column prefixes in InnoDB tables
- could cause table corruption. (Bug #28138)
-
-
-
-
-
- INSERT INTO ... SELECT caused a crash if
- innodb_locks_unsafe_for_binlog was enabled.
- (Bug #27294)
-
-
-
-
-
- SHOW INNODB STATUS caused an assertion
- failure under high load. (Bug #22819)
-
-
-
-
-
- If a slave timed out while registering with the master to
- which it was connecting, auto-reconnect failed thereafter.
- (Bug #19328)
-
-
-
-
-
- For the embedded server, the
- mysql_stmt_store_result() C API function
- caused a memory leak for empty result sets. (Bug #29687)
-
-
-
-
-
- mysql-stress-test.pl and
- mysqld_multi.server.sh were missing from
- some binary distributions. (Bug #21023, Bug #25486)
-
-
-
-
-
SELECT ... INTO OUTFILE followed by
LOAD DATA could result in garbled
characters when the FIELDS ENCLOSED BY
-- MySQL Code Commits Mailing List For list archives: http://lists.mysql.com/commits To unsubscribe: http://lists.mysql.com/commits?unsub=lists@pantek.comReceived on Tue Jul 31 15:21:45 2007
This archive was generated by hypermail 2.1.8 : Thu Aug 09 2007 - 19:20:09 EDT
|
Contact Us Legal Notices Order Services Online Pantek Home Privacy Policy IT news Site Map Pantek Library |