MySQL is een krachtige opensource 'relational database management system' die met name populair is als website- en forumdatabase. Ook Tweakers.net maakt gebruik van MySQL om onder andere gebruikersgegevens, statistieken en de diverse review-, meuk- en nieuwsartikelen op te slaan. De ontwikkelaars hebben twee nieuwe versies in de 5.0-tak uitgebracht, namelijk MySQL Community Server 5.0.81 en MySQL Enterprise 5.0.80 MRU. Voor een overzicht van de verschillen tussen de twee smaken verwijzen we jullie door naar dit overzicht. De bijbehorende aankondigingen van deze uitgaves zien er als volgt uit:
Release Notes for MySQL Enterprise 5.0.80 MRU
This is a Monthly Rapid Update release of the MySQL Enterprise Server 5.0.
This section documents all changes and bugfixes that have been applied since the last MySQL Enterprise Server release (5.0.79). If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Enterprise (a commercial MySQL offering).
Support Ending for AIX 5.2: Per the MySQL Support Lifecycle policy regarding ending support for OS versions that have reached vendor end of life, we plan to discontinue building or supporting MySQL binaries for AIX 5.2 as of April 30, 2009. The next release of MySQL 5.0 (5.0.80) will be the last MySQL 5.0 release with support for AIX 5.2.
Functionality added or changed:
- The MD5 algorithm now uses the Xfree implementation. (Bug#42434)
- Replication: An INSERT DELAYED into a TIMESTAMP column issued concurrently with a an insert on the same column not using DELAYED, but applied after the other insert, was logged using the same timestamp as generated by the other (non-DELAYED) insert. (Bug#41719)
- An attempt by a user who did not have the SUPER privilege to kill a system thread could cause a server crash. (Bug#43748)
- Use of USE INDEX hints could cause EXPLAIN EXTENDED to crash. (Bug#43354)
- mysql crashed if a request for the current database name returned an empty result, such as after the client has executed a preceding SET sql_select_limit=0 statement. (Bug#43254)
- The strings/CHARSET_INFO.txt file was not included in source distributions. (Bug#42937)
- mysqldump included views that were excluded with the --ignore-table option. (Bug#42635)
- Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak. (Bug#42502)
- With more than two arguments, LEAST(), GREATEST(), and CASE could unnecessarily return Illegal mix of collations errors. (Bug#41627)
- The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug#41486)
- In the help command output displayed by mysql, the description for the \c (clear) command was misleading. (Bug#41268)
- The use of NAME_CONST() can result in a problem for CREATE TABLE ... SELECT statements when the source column expressions refer to local variables. Converting these references to NAME_CONST() expressions can result in column names that are different on the master and slave servers, or names that are too long to be legal column identifiers. A workaround is to supply aliases for columns that refer to local variables. Now a warning is issued in such cases that indicate possible problems. (Bug#35383)
- The Time column for SHOW PROCESSLIST output now can have negative values. Previously, the column was unsigned and negative values were displayed incorrectly as large positive values. Negative values can occur if a thread alters the time into the future with SET TIMESTAMP = value or the thread is executing on a slave and processing events from a master that has its clock set ahead of the slave. (Bug#22047)
- Restoring a mysqldump dump file containing FEDERATED tables failed because the file contained the data for the table. Now only the table definition is dumped (because the data is located elsewhere). (Bug#21360)
Release Notes for MySQL Community Server 5.0.81
This is a bugfix release for the current production release family. It replaces MySQL 5.0.77.
Functionality added or changed:
- Security Enhancement: To enable stricter control over the location from which user-defined functions can be loaded, the plugin_dir system variable has been backported from MySQL 5.1. If the value is non-empty, user-defined function object files can be loaded only from the directory named by this variable. If the value is empty, the behavior that is used prior to the inclusion of plugin_dir applies: The UDF object files must be located in a directory that is searched by your system's dynamic linker. (Bug#37428)
- A new status variable, Queries, indicates the number of statements executed by the server. This includes statements executed within stored programs, unlike the Questions variable which includes only statements sent to the server by clients. (Bug#41131)
- Previously, index hints did not work for FULLTEXT searches. Now they work as follows: For natural language mode searches, index hints are silently ignored. For example, IGNORE INDEX(i) is ignored with no warning and the index is still used. For boolean mode searches, index hints are honored. (Bug#38842)
- See the list on this page.