JP
このバージョンをダウンロードする
39.06MB
|
MySQL 5.1.45MySQL AB - 39.06MB (オープンソース) |
# Bugs fixed:
* Partitioning: Attempting to drop a partitioned table from one connection while waiting for the completion of an ALTER TABLE that had been issued from a different connection, and that changed the storage engine used by the table, could cause the server to crash. (Bug#42438)
* Replication: Adding an index to a table on the master caused the slave to stop logging slow queries to the slow query log. (Bug#50620)
* Replication: Queries which were written to the slow query log on the master were not written to the slow query log on the slave. (Bug#23300) See also Bug#48632.
* mysqld_multi failed due to a syntax error in the script. (Bug#51468)
* Referring to a subquery result in a HAVING clause could produce incorrect results. (Bug#50995)
* Use of filesort plus the join cache normally is preferred to a full index scan. But it was used even if the index is clustered, in which case, the clustered index scan can be faster. (Bug#50843)
* For debug builds, SHOW BINARY LOGS caused an assertion to be raised if binary logging was not enabled. (Bug#50780)
* Incorrect handling of BIT columns in temporary tables could lead to spurious duplicate-key errors. (Bug#50591)
* Full-text queries that used the truncation operator (*) could enter an infinite loop. (Bug#50351)
* mysqltest no longer lets you execute an SQL statement on a connection after doing a send command, unless you do a reap first. This was previously accepted but could produce unpredictable results. (Bug#49269)
* For debug builds on Windows, warnings about incorrect use of debugging directives were written to the error log. The directives were rewritten to eliminate these messages. (Bug#49025)
* Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)
* An ARZ file missing from the database directory caused the server to crash. (Bug#48757)
* Slow CALL statements were not always logged to the slow query log because execution time for multiple-statement stored procedures was assessed incorrectly. (Bug#47905)
* Failure to open a view with a nonexistent DEFINER was improperly handled and the server would crash later attempting to lock the view. (Bug#47734)
* If EXPLAIN encountered an error in the query, a memory leak occurred. (Bug#45989)
* Grouping by a subquery in a query with a DISTINCT aggregate function led to incorrect and unordered grouping values. (Bug#45640)
* Propagation of a large unsigned numeric constant in WHERE expressions could lead to incorrect results. This also affected EXPLAIN EXTENDED, which printed incorrect numeric constants in such transformed WHERE expressions. (Bug#45360)
* Valgrind warnings about uninitialized variables in optimizer code were silenced. (Bug#45195)
* flush_cache_records() did not correctly check for errors that should cause statement execution to stop, leading to a server crash. (Bug#39022)
* When building MySQL when using a different target directory (for example using the VPATH environment variable), the build of the embedded readline component would fail. (Bug#35250)
* INSERT INTO ... VALUES(DEFAULT) failed to insert the correct value for ENUM columns. For MyISAM tables, an empty value was inserted. For CSV tables, the table became corrupt. (Bug#33717)
* Partitioning: Attempting to drop a partitioned table from one connection while waiting for the completion of an ALTER TABLE that had been issued from a different connection, and that changed the storage engine used by the table, could cause the server to crash. (Bug#42438)
* Replication: Adding an index to a table on the master caused the slave to stop logging slow queries to the slow query log. (Bug#50620)
* Replication: Queries which were written to the slow query log on the master were not written to the slow query log on the slave. (Bug#23300) See also Bug#48632.
* mysqld_multi failed due to a syntax error in the script. (Bug#51468)
* Referring to a subquery result in a HAVING clause could produce incorrect results. (Bug#50995)
* Use of filesort plus the join cache normally is preferred to a full index scan. But it was used even if the index is clustered, in which case, the clustered index scan can be faster. (Bug#50843)
* For debug builds, SHOW BINARY LOGS caused an assertion to be raised if binary logging was not enabled. (Bug#50780)
* Incorrect handling of BIT columns in temporary tables could lead to spurious duplicate-key errors. (Bug#50591)
* Full-text queries that used the truncation operator (*) could enter an infinite loop. (Bug#50351)
* mysqltest no longer lets you execute an SQL statement on a connection after doing a send command, unless you do a reap first. This was previously accepted but could produce unpredictable results. (Bug#49269)
* For debug builds on Windows, warnings about incorrect use of debugging directives were written to the error log. The directives were rewritten to eliminate these messages. (Bug#49025)
* Building MySQL on Fedora Core 12 64-bit failed, due to errors in comp_err. (Bug#48864)
* An ARZ file missing from the database directory caused the server to crash. (Bug#48757)
* Slow CALL statements were not always logged to the slow query log because execution time for multiple-statement stored procedures was assessed incorrectly. (Bug#47905)
* Failure to open a view with a nonexistent DEFINER was improperly handled and the server would crash later attempting to lock the view. (Bug#47734)
* If EXPLAIN encountered an error in the query, a memory leak occurred. (Bug#45989)
* Grouping by a subquery in a query with a DISTINCT aggregate function led to incorrect and unordered grouping values. (Bug#45640)
* Propagation of a large unsigned numeric constant in WHERE expressions could lead to incorrect results. This also affected EXPLAIN EXTENDED, which printed incorrect numeric constants in such transformed WHERE expressions. (Bug#45360)
* Valgrind warnings about uninitialized variables in optimizer code were silenced. (Bug#45195)
* flush_cache_records() did not correctly check for errors that should cause statement execution to stop, leading to a server crash. (Bug#39022)
* When building MySQL when using a different target directory (for example using the VPATH environment variable), the build of the embedded readline component would fail. (Bug#35250)
* INSERT INTO ... VALUES(DEFAULT) failed to insert the correct value for ENUM columns. For MyISAM tables, an empty value was inserted. For CSV tables, the table became corrupt. (Bug#33717)
NetBeans IDE 7.3.1
Virtual PC 2007 SP1
VMware Player 5.0.2
SQL Server 2012 Express
Notepad++ 6.3.3
VirtualBox 4.2.12.84980
Eclipse Classic 4.2.2 (64-bit)
NSIS 2.46
Blue Griffon 1.5.2
Sublime Text 2.0.1
このページのリンクを作成するには以下のコードをコピーしてください：
![Scientists are getting very close to creating an actual invisibility cloak, as separate research teams over the past week have revealed significant advancements in the area. From an invisibility cloak scaled up to be able to hide a person to a quantum invisibility cloak that can hide objects in time, there is no better moment for fans of H.G. Wells and the Harry Potter franchise than this one. The invisibility cloak that uses time was designed by Purdue University scientists. Unlike the spatial cloak we all saw in Harry Potter, this device uses time cloaking, a relatively new concept based on the idea that in some places in time, the things that happen are not picked up. Since nobody can tell that these things occurred, it’s like they never happened. The concept still has a long way to go before it turns into reality, although scientists have been able to cloak small electrical signals so far. The technology may be difficult to grasp, yet researchers think that if successful , it will be a major breakthrough in making quantum information computing and storage very successful. Another research team, meanwhile, detailed how to make an invisibility cloak to hide large objects, including a person. The New York University of Rochester scientists used a conventional arrangement of lenses and mirrors to drive the light around the area they want to hide from view. The human-scale cloak also manages the impressive feat of hiding items across the entire optical range. But it still faces one major problem: that is only works in one direction, which means the hidden object becomes visible if the viewpoint changes. Nonetheless, this large-scale cloak could be successfully used to hide satellites in orbit and other huge objects. And a Shanghai-based team of researchers unveiled another invisibility cloak which they claim can be adjusted to make items invisible from any line of sight. The scientists demonstrated the cloak by making a pet goldfish and a cat disappear. According to the Chinese team, the device may have important applications in security, surveillance and entertainment. http://www.youtube.com/watch?v=YNO9-DYCi2U With all the new ideas and research, it seems we will see an actual invisibility cloak in use very soon. What do you think of this technology? What would you do if you had your very own invisibility cloak? [Image via Mental floss]](http://cdn.techbeat.com/wp-content/uploads/2013/06/invisibility-harry-120x80.jpg)