- News -
MySQL : MySQL 5.1.14-beta リリース
投稿者： webmaster 投稿日時： 2006-12-12 12:19:53 (73056 ヒット)

MySQL 5.1.14-beta がリリースされました。

　http://dev.mysql.com/downloads/

からダウンロードできます。

5.1.13 はリリースされませんでしたので、5.1.12から約１ヶ月ぶりの バージョン 5.1 シリーズ のリリースになります。

２バージョンぶんの変更が含まれているので（わずか１ヶ月ですが）、チェンジログが非常にもりだくさんになっています。

------
以下チェンジログ

■機能の追加と変更(5.1.14)
- Incompatible change: Previously, you could create a user-defined function (UDF) or stored function with the same name as a built-in function, but could not invoke the UDF. Now an error occurs if you try to create such a UDF. The server also now generates a warning if you create a stored function with the same name as a built-in function. It is not considered an error to create a stored function with the same name as a built-in function because you can invoke the function using db_name.func_name() syntax. However, the server now generates a warning in this case. (Bug#22619: http://bugs.mysql.com/22619) See Section 9.2.4, "Function Name Resolution," for the rules describing how the server interprets references to different kinds of functions.

- NDB Cluster (Replication): ndb_restore now creates the apply_status and schema tables if they do not already exist on the slave cluster. (Bug#14612: http://bugs.mysql.com/14612)

- NDB Cluster: Backup messages are now printed to the Cluster log. (Bug#24544: http://bugs.mysql.com/24544)

- NDB Cluster: The error message Management server closed connection, when recorded in the MySQL error log, now includes a timestamp indicating when the error took place. (Bug#21519: http://bugs.mysql.com/21519)

- NDB Cluster (Disk Data): The output of mysqldump now includes by default all tablespace and logfile group definitions used by any tables or databases that are dumped. (Bug#20839: http://bugs.mysql.com/20839) Note: The working of the --all-tablespaces or -Y option for mysqldump remains unaffected by this change.

- Direct and indirect usage of stored routines, user-defined functions, and table references is now prohibited in CREATE EVENT and ALTER EVENT statements. (Bug#22830: http://bugs.mysql.com/22830) See Section 20.2.1, "CREATE EVENT Syntax," and Section 20.2.2, "ALTER EVENT Syntax," for more specific information.

- DROP TRIGGER now supports an IF EXISTS clause. (Bug#23703: http://bugs.mysql.com/23703)


■バグ修正(5.1.14)：
- NDB Cluster (Replication): If errors occurred during purging of the binary logs, extraneous rows could remain left in the binlog_index table. (Bug#15021: http://bugs.mysql.com/15021)

- NDB Cluster (Disk Data): ndb_restore could sometimes fail when attempting to restore Disk Data tables due to data node failure caused by accessing unitialized memory. (Bug#24331: http://bugs.mysql.com/24331)

- NDB Cluster (Disk Data): Excessive fragmentation of Disk Data files (including log files and data files) could occur during the course of normal use. (Bug#24143: http://bugs.mysql.com/24143)

- NDB Cluster (Disk Data): It was possible to execute a statement for creating a Disk Data table that referred to a nonexistent tablespace, in which case the table was an in-memory NDB table. Such a statement instead now fails with an appropriate error message. (Bug#23576: http://bugs.mysql.com/23576)

- NDB Cluster (Disk Data): Under some circumstances, a DELETE from a Disk Data table could cause mysqld to crash. (Bug#23542: http://bugs.mysql.com/23542)

- NDB Cluster (Cluster APIs): Using BIT values with any of the comparison methods of the NdbScanFilter class caused the cluster's data nodes to fail. (Bug#24503: http://bugs.mysql.com/24503)

- NDB Cluster: A value equal to or greater than the allowed maximum for LongMessageBuffer caused all data nodes to crash. (Bug#22547: http://bugs.mysql.com/22547)

- NDB Cluster: The failure of a data node failure during a schema operation could lead to additional node failures. (Bug#24752: http://bugs.mysql.com/24752)

- NDB Cluster: A committed read could be attempted before a data node had time to connect, causing a timeout error. (Bug#24717: http://bugs.mysql.com/24717)

- NDB Cluster: The simultaneous shutdown of mysqld and ndbd processes caused unnecessary locking. (Bug#24655: http://bugs.mysql.com/24655)

- NDB Cluster: The failure of the master node in a node group during the allocation of node IDs could cause ndb_mgmd to hang. (Bug#24543: http://bugs.mysql.com/24543)

- NDB Cluster: In certain rare cases, a data node could crash due to a typographical error in the MySQL Cluster source code. (Bug#24476: http://bugs.mysql.com/24476)

- NDB Cluster: Creating a new tables containing a BLOB column when the server was short of memory could cause the server to crash. (Bug#24470: http://bugs.mysql.com/24470)

- NDB Cluster: Any statement following the execution of CREATE TABLE ... LIKE ndb_table (where ndb_table was a table using the NDB storage engine), would cause the mysql client to hang. (Bug#24301: http://bugs.mysql.com/24301)

- NDB Cluster: When the management client command ALL RESTART -i was executed while one data node was not running, all data nodes in the cluster were shut down. (Bug#24105: http://bugs.mysql.com/24105)

- NDB Cluster: A query using an index scan followed by a delete operation, and then a rollback could cause one or more data nodes to crash. (Bug#24039: http://bugs.mysql.com/24039)

- NDB Cluster (Cluster APIs): Some MGM API function calls could yield incorrect return values in certain cases where the cluster was operating under a very high load, or experienced timeouts in inter-node communications. (Bug#24011: http://bugs.mysql.com/24011)

- NDB Cluster: It was possible for the sum of the MaxNoOfTables, MaxNoOfOrderedIndexes, and MaxNoOfUniqueHashIndexes configuration parameters, plus the number of system tables to exceed the maximum value for a Uint32 number. In such a case, the cluster's data nodes failed to start, and no reason for this could easily be determined from the error messages provided. (Bug#22548: http://bugs.mysql.com/22548)

- NDB Cluster: Given a table mytbl in a database mydb on a MySQL Server acting as an SQL node in a MySQL Cluster, then, following multiple ALTER TABLE mytbl ENGINE=engine statements --- first, to change the storage engine used for a table to NDB, and then again to change the table to use a non-NDB storage engine --- a DROP DATABASE mydb statement executed on any SQL node in the cluster would cause mydb to be dropped on all SQL nodes in the cluster, even if mydb contained non-NDB tables. (Bug#21495: http://bugs.mysql.com/21495)

- NDB Cluster: An incorrect error message was displayed in the event that the value of the MaxNoOfOrderedIndexes parameter was set too low. (Bug#20065: http://bugs.mysql.com/20065)

- NDB Cluster: An incorrect error message was displayed in the event that the value of the DataMemory parameter was insufficient for the amount of data to be stored by the cluster. (Bug#19808: http://bugs.mysql.com/19808)

- NDB Cluster: A unique constraint violation was not ignored by an UPDATE IGNORE statement when the constraint violation occurred on a non-primary key. (Bug#18487: http://bugs.mysql.com/18487, Bug#24303: http://bugs.mysql.com/24303)

- Through the C API, the member strings in MYSQL_FIELD for a query that contains expressions may return incorrect results. (Bug#21635: http://bugs.mysql.com/21635)

- mysql_affected_rows() could return values different from mysql_stmt_affected_rows() for the same sequence of statements. (Bug#23383: http://bugs.mysql.com/23383)

- IN() and CHAR() can return NULL, but did not signal that to the query processor, causing incorrect results for IS NULL operations. (Bug#17047: http://bugs.mysql.com/17047)

- Instance Manager option-parsing code caused memory-allocation errors. (Bug#22242: http://bugs.mysql.com/22242)

- A trigger that invoked a stored function could cause a server crash when activated by different client connections. (Bug#23651: http://bugs.mysql.com/23651)

- CONCURRENT did not work correctly for LOAD DATA INFILE. (Bug#20637: http://bugs.mysql.com/20637)

- A stored procedure, executed from a connection using a binary character set, and which wrote multi-byte data, would write incorrectly escaped entries to the binary log. This caused syntax errors, and caused replication to fail. (Bug#23619: http://bugs.mysql.com/23619)

- The server source code had multiple exportable definitions of the field_in_record_is_null() function. These are now all declared static. (Bug#24190: http://bugs.mysql.com/24190)

- When reading from the standard input on Windows, mysqlbinlog opened the input in text mode rather than binary mode and consequently misinterpreted some characters such as Control-Z. (Bug#23735: http://bugs.mysql.com/23735)

- Inserting a default or invalid value into a spatial column could fail with Unknown error rather than a more appropriate error. (Bug#21790: http://bugs.mysql.com/21790)

- The server could send incorrect column count information to the client for queries that produce a larger number of columns than can fit in a two-byte number. (Bug#19216: http://bugs.mysql.com/19216)

- Evaluation of subqueries that require the filesort algorithm were allocating and freeing the sort_buffer_size buffer many times, resulting in slow performance. Now the buffer is allocated once and reused. (Bug#21727: http://bugs.mysql.com/21727)

- SQL statements close to the size of max_allowed_packet could produce binary log events larger than max_allowed_packet that could not be read by slave servers. (Bug#19402: http://bugs.mysql.com/19402)

- View columns were always handled as having implicit derivation, leading to illegal mix of collation errors for some views in UNION operations. Now view column column derivation comes from the original expression given in the view definition. (Bug#21505: http://bugs.mysql.com/21505)

- If elements in a non-top-level IN subquery were accessed by an index and the subquery result set included a NULL value, the quantified predicate that contained the subquery was evaluated to NULL when it should return a non-NULL value. (Bug#23478: http://bugs.mysql.com/23478)

- Calculation of COUNT(DISTINCT), AVG(DISTINCT), or SUM(DISTINCT) when they are referenced more than once in a single query with GROUP BY could cause a server crash. (Bug#23184: http://bugs.mysql.com/23184)

- For a cast of a DATETIME value containing microseconds to DECIMAL, the microseconds part was truncated without generating a warning. Now the microseconds part is preserved. (Bug#19491: http://bugs.mysql.com/19491)

- Metadata for columns calculated from scalar subqueries was limited to integer, double, or string, even if the actual type of the column was different. (Bug#11032: http://bugs.mysql.com/11032)

- The result for CAST() when casting a value to UNSIGNED was limited to the maximum signed BIGINT value, not the maximum unsigned value. (Bug#8663: http://bugs.mysql.com/8663)

- Some unnecessary Valgrind warnings were removed from the server. (Bug#24488: http://bugs.mysql.com/24488, Bug#24533: http://bugs.mysql.com/24533).

- Using EXPLAIN caused a server crash for queries that selected from INFORMATION_SCHEMA in a subquery in the FROM clause. (Bug#22413: http://bugs.mysql.com/22413)

- Invalidating the query cache caused a server crash for INSERT INTO ... SELECT statements that selected from a view. (Bug#20045: http://bugs.mysql.com/20045)

- With row-based binary logging, replicated multiple-statement transaction deadlocks did not return the correct error code, causing the slave SQL thread to stop rather than roll back and re-execute. (Bug#23831: http://bugs.mysql.com/23831)

- With row-based binary logging, for CREATE TABLE IF NOT EXISTS LIKE temporary_table statements, the IF NOT EXISTS clause was not logged. (Bug#22762: http://bugs.mysql.com/22762)

- With row-based binary logging, CREATE TABLE IF NOT EXISTS SELECT statements were not logged properly. (Bug#22027: http://bugs.mysql.com/22027)

- On slave servers, transactions that exceeded the lock wait timeout failed to roll back properly. (Bug#20697: http://bugs.mysql.com/20697)

- Changes to character set variables prior to an action on a replication-ignored table were forgotten by slave servers. (Bug#22877: http://bugs.mysql.com/22877)

- With lower_case_table_names set to 1, SHOW CREATE TABLE printed incorrect output for table names containing Turkish I (LATIN CAPITAL LETTER I WITH DOT ABOVE). (Bug#20404: http://bugs.mysql.com/20404)

- When applying the group_concat_max_len limit, GROUP_CONCAT() could truncate multi-byte characters in the middle. (Bug#23451: http://bugs.mysql.com/23451)

- For view renaming, the table name to filename encoding was not performed. (Bug#21370: http://bugs.mysql.com/21370)

- For some problems relating to character set conversion or incorrect string values for INSERT or UPDATE, the server was reporting truncation or length errors instead. (Bug#18908: http://bugs.mysql.com/18908)

- The XPath operators < and >, as implemented in the ExtractValue() function, operated in reverse. (Bug#22823: http://bugs.mysql.com/22823)

印刷用ページ このニュースを友達に送る
投稿者 スレッド
webmaster
投稿日時: 2006-12-12 12:25 
管理人
登録日: 2004-4-13
居住地:
投稿数: 3
オンライン
 5.1.13-beta( not released ) での変更
■機能の追加と変更(5.1.13(リリースされなかったバージョン))
- Binary distributions of MySQL 5.1.12 were built without support for partitioning. This has been corrected except for NetWare. (Bug#23949: http://bugs.mysql.com/23949)

- A change in the interfaces for the INFORMATION_SCHEMA.FILES table has made the table accessible to storage engines other than NDB. (Bug#23013: http://bugs.mysql.com/23013)

- mysqldump --single-transaction now uses START TRANSACTION /*!40100 WITH CONSISTENT SNAPSHOT */ rather than BEGIN to start a transaction, so that a consistent snapshot will be used on those servers that support it. (Bug#19660: http://bugs.mysql.com/19660)

- mysql_upgrade now passes all the parameters specified on the command line to both mysqlcheck and mysql using the upgrade_defaults file. (Bug#20100: http://bugs.mysql.com/20100)

- For the CALL statement, stored procedures that take no arguments now can be invoked without parentheses. That is, CALL p() and CALL p are equivalent. (Bug#21462: http://bugs.mysql.com/21462)


■バグ修正(5.1.13(リリースされなかったバージョン))

- MySQL 5.0.26 introduced an ABI incompatibility, which this release reverts. Programs compiled against 5.0.26 are not compatible with any other version and must be recompiled. (Bug#23427: http://bugs.mysql.com/23427)

- If a table contains an AUTO_INCREMENT column, inserting into an insertable view on the table that does not include the AUTO_INCREMENT column should not change the value of LAST_INSERT_ID(), because the side effects of inserting default values into columns not part of the view should not be visible. MySQL was incorrectly setting LAST_INSERT_ID() to zero. (Bug#22584: http://bugs.mysql.com/22584)

- M % 0 returns NULL, but (M % 0) IS NULL evaluated to false. (Bug#23411: http://bugs.mysql.com/23411)

- Within a stored routine, a view definition cannot refer to routine parameters or local variables. However, an error did not occur until the routine was called. Now it occurs during parsing of the routine creation statement. (Bug#20953: http://bugs.mysql.com/20953) Note: A side effect of this fix is that if you have already created such routines, and error will occur if you execute SHOW CREATE PROCEDURE or SHOW CREATE FUNCTION. You should drop these routines because they are erroneous.

- A client library crash was caused by executing a statement such as SELECT * FROM t1 PROCEDURE ANALYSE() using a server side cursor on a table t1 that does not have the same number of columns as the output from PROCEDURE ANALYSE(). (Bug#17039: http://bugs.mysql.com/17039)

- mysql did not check for errors when fetching data during result set printing. (Bug#22913: http://bugs.mysql.com/22913)

- Adding a day, month, or year interval to a DATE value produced a DATE, but adding a week interval produced a DATETIME value. Now all produce a DATE value. (Bug#21811: http://bugs.mysql.com/21811)

- The column default value in the output from SHOW COLUMNS or SELECT FROM INFORMATION_SCHEMA.COLUMNS was truncated to 64 characters. (Bug#23037: http://bugs.mysql.com/23037)

- For not-yet-authenticated connections, the Time column in SHOW PROCESSLIST was a random value rather than NULL. (Bug#23379: http://bugs.mysql.com/23379)

- The Host column in SHOW PROCESSLIST output was blank when the server was started with the --skip-grant-tables option. (Bug#22728: http://bugs.mysql.com/22728)

- The Handler_rollback status variable sometimes was incremented when no rollback had taken place. (Bug#22728: http://bugs.mysql.com/22728)

- Within a prepared statement, SELECT (COUNT(*) = 1) (or similar use of other aggregate functions) did not return the correct result for statement re-execution. (Bug#21354: http://bugs.mysql.com/21354)

- Lack of validation for input and output TIME values resulted in several problems: SEC_TO_TIME() within subqueries incorrectly clipped large values; SEC_TO_TIME() treated BIGINT UNSIGNED values as signed; only truncation warnings were produced when both truncation and out-of-range TIME values occurred. (Bug#11655: http://bugs.mysql.com/11655, Bug#20927: http://bugs.mysql.com/20927)

- Range searches on columns with an index prefix could miss records. (Bug#20732: http://bugs.mysql.com/20732)

- With SQL_MODE=TRADITIONAL, MySQL incorrectly aborted on warnings within stored routines and triggers. (Bug#20028: http://bugs.mysql.com/20028)

- In mysql, invoking connect or \r with very long db_name or host_name parameters caused buffer overflow. (Bug#20894: http://bugs.mysql.com/20894)

- mysqldump --xml produced invalid XML for BLOB data. (Bug#19745: http://bugs.mysql.com/19745)

- For a debug server, a reference to an undefined user variable in a prepared statment executed with EXECUTE caused an assertion failure. (Bug#19356: http://bugs.mysql.com/19356)

- Within a trigger for a base table, selecting from a view on that base table failed. (Bug#19111: http://bugs.mysql.com/19111)

- DELETE IGNORE could hang for foreign key parent deletes. (Bug#18819: http://bugs.mysql.com/18819)

- Transient errors in replication from master to slave may trigger multiple Got fatal error 1236: 'binlog truncated in the middle of event' errors on the slave. (Bug#4053: http://bugs.mysql.com/4053)

- The value of the warning_count system variable was not being calculated correctly (also affecting SHOW COUNT(*) WARNINGS). (Bug#19024: http://bugs.mysql.com/19024)

- InnoDB showed substandard performance with multiple queries running concurrently. (Bug#15815: http://bugs.mysql.com/15815)

- There was a race condition in the InnoDB fil_flush_file_spaces() function. (Bug#24098: http://bugs.mysql.com/24098)

- FROM_UNIXTIME() did not accept arguments up to POWER(2,31)-1, which it had previously. (Bug#9191: http://bugs.mysql.com/9191)

- Some yaSSL-related memory leaks detected by Valgrind were fixed. (Bug#23981: http://bugs.mysql.com/23981)

- If COMPRESS() returned NULL, subsequent invocations of COMPRESS() within a result set or within a trigger also returned NULL. (Bug#23254: http://bugs.mysql.com/23254)

- mysql would lose its connection to the server if its standard output was not writable. (Bug#17583: http://bugs.mysql.com/17583)

- mysql-test-run did not work correctly for RPM-based installations. (Bug#17194: http://bugs.mysql.com/17194)

- The return value from my_seek() was ignored. (Bug#22828: http://bugs.mysql.com/22828)

- Use of PREPARE with a CREATE PROCEDURE statement that contained a syntax error caused a server crash. (Bug#21868: http://bugs.mysql.com/21868)

- Use of a DES-encrypted SSL certificate file caused a server crash. (Bug#21868: http://bugs.mysql.com/21868)

- Column names were not quoted properly for replicated views. (Bug#19736: http://bugs.mysql.com/19736)

- InnoDB used table locks (not row locks) within stored functions. (Bug#18077: http://bugs.mysql.com/18077)

- InnoDB crashed when trying to display an error message about a foreign key constraint violation when the two tables are in different schemas. (Bug#23368: http://bugs.mysql.com/23368)

- Statements such as DROP PROCEDURE and DROP VIEW were written to the binary log too late due to a race condition. (Bug#14262: http://bugs.mysql.com/14262)

- At shutdown, Instance Manager told guarded server instances to stop, but did not wait until they actually stopped. (Bug#17486: http://bugs.mysql.com/17486)

- It was not possible to do an atomic rename of the log tables without the possibility of losing rows. Now you can do this:
USE mysql;
CREATE TABLE IF NOT EXISTS general_log2 LIKE general_log;
RENAME TABLE general_log TO general_log_backup, general_log2 TO general_log; (Bug#17544: http://bugs.mysql.com/17544, Bug#21785: http://bugs.mysql.com/21785)


- NDB Cluster (Disk Data): In the event of an aborted multiple update, the space in the Disk Data log buffer to be freed as a result was actually freed twice, which could eventually lead to a crash. (Bug#23430: http://bugs.mysql.com/23430)

- NDB Cluster: An NDB source file included a memset() call with reversed arguments. (Bug#23169: http://bugs.mysql.com/23169)

- NDB Cluster: Under some conditions, the data distribution could become unbalanced in a MySQL Cluster with 2 or more node groups following the creation of a new table. (Bug#21690: http://bugs.mysql.com/21690) As part of the fix for this bug, two new NDB API methods were added to the NdbDictionary::Object::Table class. See the MySQL Cluster API documentation for details.

- Incorrect warnings occurred for use of CREATE TABLE ... LIKE or REPAIR TABLE with the log tables. (Bug#21966: http://bugs.mysql.com/21966)

- MySQL failed to build on the Alpha platform. (Bug#23256: http://bugs.mysql.com/23256)

- The optimizer failed to use equality propagation for BETWEEN and IN predicates with string arguments. (Bug#22753: http://bugs.mysql.com/22753)

- The optimizer used the ref join type rather than eq_ref for a simple join on strings. (Bug#22367: http://bugs.mysql.com/22367)

- The WITH CHECK OPTION for a view failed to prevent storing invalid column values for UPDATE statements. (Bug#16813: http://bugs.mysql.com/16813)

- A literal string in a GROUP BY clause could be interpreted as a column name. (Bug#14019: http://bugs.mysql.com/14019)

- Some queries that used MAX() and GROUP BY could incorrectly return an empty result. (Bug#22342: http://bugs.mysql.com/22342)

- WITH ROLLUP could group unequal values. (Bug#20825: http://bugs.mysql.com/20825)

- Use of a subquery that invoked a function in the column list of the outer query resulted in a memory leak. (Bug#21798: http://bugs.mysql.com/21798)

- LIKE searches failed for indexed utf8 character columns. (Bug#20471: http://bugs.mysql.com/20471)

- FLUSH INSTANCES in Instance Manager triggered an assertion failure. (Bug#19368: http://bugs.mysql.com/19368)

- ALTER TABLE was not able to rename a view. (Bug#14959: http://bugs.mysql.com/14959)

- The optimizer sometimes mishandled R-tree indexes for GEOMETRY data types, resulting in a server crash. (Bug#21888: http://bugs.mysql.com/21888)

- An unhandled NULL pointer caused a server crash. (Bug#22138: http://bugs.mysql.com/22138)

- Use of SQL_BIG_RESULT did not influence the sort plan for query execution. (Bug#22781: http://bugs.mysql.com/22781)

- The server did not allocate sufficient memory for some queries for which a DISTINCT to GROUP BY conversion is possible and an ORDER BY clause is present, resulting in a server crash. (Bug#20503: http://bugs.mysql.com/20503)

- The range analysis optimizer did not take into account predicates for which an index could be used after reading const tables. In some cases this resulted in non-optimal execution plans. (Bug#19579: http://bugs.mysql.com/19579)

- Entries in the slow query log could have an incorrect Rows_examined value. (Bug#12240: http://bugs.mysql.com/12240)

- Insufficient memory (myisam_sort_buffer_size) could cause a server crash for several operations on MyISAM tables: repair table, create index by sort, repair by sort, parallel repair, bulk insert. (Bug#23175: http://bugs.mysql.com/23175)

- OPTIMIZE TABLE with myisam_repair_threads > 1 could result in MyISAM table corruption. (Bug#8283: http://bugs.mysql.com/8283)

- NDB Cluster: Restoring a cluster failed if there were any tables with 128 or more columns. (Bug#23494: http://bugs.mysql.com/23494, Bug#23502: http://bugs.mysql.com/23502)

- NDB Cluster: Cluster backups would fail when there were more than 2048 schema objects in the cluster. (Bug#23499: http://bugs.mysql.com/23499)

- NDB Cluster: The management client command ALL DUMP 1000 would cause the cluster to crash if data nodes were connected to the cluster but not yret fully started. (Bug#23203: http://bugs.mysql.com/23203)

- NDB Cluster: INSERT ... ON DUPLICATE KEY UPDATE on an NDB table could lead to deadlocks and memory leaks. (Bug#23200: http://bugs.mysql.com/23200)

- NDB Cluster: If a node restart could not be performed from the REDO log, no node takeover took place. This could cause partitions to be left empty during a system restart. (Bug#22893: http://bugs.mysql.com/22893)

- NDB Cluster: Multiple node restarts in rapid succession could cause a system restart to fail (Bug#22892: http://bugs.mysql.com/22892), or induce a race condition (Bug#23210: http://bugs.mysql.com/23210).

- NDB Cluster: Attempting to create a unique constraint with USING HASH on an NDB table caused mysqld to crash. (Bug#21873: http://bugs.mysql.com/21873)

- NDB Cluster: When inserting a row into an NDB table with a duplicate value for a non-primary unique key, the error issued would reference the wrong key. (Bug#21072: http://bugs.mysql.com/21072)

- NDB Cluster (NDB API): When multiple processes or threads in parallel performed the same ordered scan with exclusive lock and updating the retrieved records, the scan could skip some records, which were not updated as the result. (Bug#20446: http://bugs.mysql.com/20446)

- NDB Cluster: Aborting a cluster backup too soon after starting it caused a forced shutdown of the data nodes. (Bug#19148: http://bugs.mysql.com/19148)
[AD]