List:Packagers« Previous MessageNext Message »
From:Lenz Grimmer Date:August 12 2005 4:34pm
Subject:MySQL 5.0.11-beta has been released
View as plain text  
Hash: SHA1


MySQL 5.0.11-beta, a new version of the popular Open Source Database Management
System, has been released. The Community Edition is now available in source and
binary form for a number of platforms from our download pages at and mirror sites.

Note that not all mirror sites may be up to date at this point in time - if you
can't find this version on some mirror, please try again later or choose
another download site.

This is the seventh published Beta release in the 5.0 series. All attention
will continue to be focused on fixing bugs and stabilizing 5.0 for later
production release.

NOTE: This Beta release, as any other pre-production release, should not be
installed on ``production'' level systems or systems with critical data. It is
good practice to back up your data before installing any new version of
software. Although MySQL has done its best to ensure a high level of quality,
protect your data by making a backup as you would for any software beta

Please refer to our bug database at for more details
about the individual bugs fixed in this version.

Functionality added or changed:

 * Security improvement: Applied a patch that addresses a potential
   zlib data vulnerability that could result in an application crash.
   (CAN-2005-1849 (
   This only affects the binaries for platforms that are linked statically
   against the bundled zlib (most notably Microsoft Windows and HP-UX).
 * SHOW CHARACTER SET and INFORMATION_SCHEMA now properly report the Latin1
   character set as cp1252. (Bug #11216 (
 * mysqldump now dumps triggers for each dumped table. This can be
   suppressed with the --skip-triggers option.
   (Bug #10431 (
 * Added new ER_STACK_OVERRUN_NEED_MORE error message to indicate that,
   while the stack is not completely full, more stack space is required.
   (Bug #11213 (
 * NDB: Improved handling of the configuration variables
   NoOfPagesToDiskDuringRestartACC, NoOfPagesToDiskAfterRestartACC,
   NoOfPagesToDiskDuringRestartTUP, and NoOfPagesToDiskAfterRestartTUP
   should result in noticeably faster startup times for MySQL Cluster.
   (Bug #12149 (
 * Added support of where clause for queries with FROM DUAL.
   (Bug #11745 (
 * Added an optimization that avoids key access with NULL keys for the ref
   method when used in outer joins. (Bug #12144 (
 * Maximum size of stored procedures increased from 64k to 4Gb.
   (Bug #11602 (
 * Added error message for users who attempt CREATE TABLE ... LIKE and
   specify a non-table in the LIKE clause.
   (Bug #6859 (

Bugs fixed:

 * Creation of the mysql group account failed during the RPM installation.
   (Bug #12348 (
 * big5 strings were not being stored in FULLTEXT index.
   (Bug #12075 (
 * When DROP DATABASE was called concurrently with a DROP TABLE of any
   table the MySQL Server crashed. (Bug #12212 (
 * max_connections_per_hour setting was being capped by unrelated
   max_user_connections setting. (Bug #9947 (
 * SELECT @@local... returned @@session... in the column header.
   (Bug #10724 (
 * Multiplying ABS() output by a negative number would return incorrect
   results. (Bug #11402 (
 * Updated dependency list for RPM builds to include missing dependencies
   such as useradd and groupadd. (Bug #12233 (
 * mysql_install_db used static localhost value in GRANT tables even when
   server hostname is not localhost, such as localhost.localdomain. This
   change is applied to version 5.0.10b on Windows.
   (Bug #11822 (
 * Multiple SELECT SQL_CACHE queries in a stored procedure causes error and
   client hang. (Bug #6897 (
 * Added checks to prevent error when allocating memory when there was
   insufficient memory available. (Bug #7003 (
 * Character data truncated when GBK characters 0xA3A0 and 0xA1 are
   present. (Bug #11987 (
 * Comparisons like SELECT "A\\" LIKE "A\\"; fail when using SET NAMES
   utf8;. (Bug #11754 (
 * Corrected inaccurate error message when inserting out of range data
   under TRADITIONAL SQL mode. (Bug #11546 (
 * When used in a SELECT query against a view, the GROUP_CONCAT() function
   returned only a single row. (Bug #11412 (
 * Calling the C API function mysql_stmt_fetch() after all rows of a result
   set were exhausted would return an error instead of MYSQL_NO_DATA.
   (Bug #11037 (
 * Information about a trigger was not displayed in the output of SELECT
   ... FROM INFORMATION_SCHEMA.TRIGGERS when the selected database was
   INFORMATION_SCHEMA, prior to the trigger's first invocation.
   (Bug #12127 (
 * Issuing successive FLUSH TABLES WITH READ LOCK would cause the mysql
   client to hang. (Bug #11934 (
 * In stored procedures, a cursor that fetched an empty string into a
   variable would set the variable to NULL instead.
   (Bug #8692 (
 * A trigger dependent on a feature of one SQL_MODE setting would cause an
   error when invoked after the SQL_MODE was changed.
   (Bug #5891 (
 * A delayed insert that would duplicate an existing record crashed the
   server instead. (Bug #12226 (
 * ALTER TABLE when SQL_MODE = 'TRADITIONAL' gave rise to an invalid error
   message. (Bug #11964 (
 * Attempting to repair a table having a fulltext index on a column
   containing words whose length exceeded 21 characters and where
   myisam_repair_threads was greater than 1 would crash the server.
   (Bug #11684 (
 * The MySQL Cluster backup log was invalid where the number of Cluster
   nodes was not equal to a power of 2.
   (Bug #11675 (
 * GROUP_CONCAT() sometimes returned a result with a different collation
   that that of its arguments. (Bug #10201 (
 * The LPAD() and RPAD() functions returned the wrong length to
   mysql_fetch_fields(). (Bug #11311 (
 * A UNIQUE VARCHAR column would be mis-identified as MUL in table
   descriptions. (Bug #11227 (
 * Incorrect error message displayed if user attempted to create a table in
   a non-existing database using CREATE database_name.table_name syntax.
   (Bug #10407 (
 * InnoDB: Do not flush after each write, not even before setting up the
   doublewrite buffer. Flushing can be extremely slow on some systems.
   (Bug #12125 (
 * InnoDB: True VARCHAR: Return NULL columns in the format expected by
   MySQL. (Bug #12186 (
 * Two threads could potentially initialize different characters sets and
   overwrite each other. (Bug #12109 (
 * Unsigned LONG system variables may return incorrect value when retreived
   with a SELECT for certain values.
   (Bug #10351 (
 * Prepared statements were not being written to the Slow Query log.
   (Bug #9968 (

- -- 
 Lenz Grimmer <lenz@stripped>
 Senior Production Engineer
 MySQL GmbH,
 Hamburg, Germany
 Are you MySQL certified?
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: For info see

MySQL 5.0.11-beta has been releasedLenz Grimmer12 Aug