MySQL Community Server 5.5.16 has been released
ABLE and REPAIR TABLE failed to find problems with MERGE tables that had underlying tables missing or with the wrong storage engine. Issues were reported only for the first underlying table. (Bug #11754210) * Replication: Processing of corrupted table map events could cause the server to crash. This was especially likely if the events mapped different tables to the same identifier, such as could happen due to Bug#56226. Now, before applying a table map event, the server checks whether the table has already been mapped with different settings, and if so, an error is raised and the slave SQL thread stops. If it has been mapped with the same settings, or if the table is set to be ignored by filtering rules, there is no change in behavior: the event is skipped and IDs are not checked. (Bug #44360, Bug #11753004) See also Bug #11763509. * For a lower_case_table_names value of 1 or 2 and a database having a mixed-case name, calling a stored function using a fully qualified name including the database name failed. (Bug #60347, Bug #11840395) * Previously, Performance Schema table columns that held byte counts were BIGINT UNSIGNED. These were changed to BIGINT (signed). This makes it easier to perform calculations that compute differences between columns. (Bug #59631, Bug #11766504) * The embedded server crashed when argc = 0. (Bug #57931, Bug #12561297) * The mysql_affected_rows() C API function returned 3 (instead of 2) for INSERT ... ON DUPLICATE KEY UPDATE statements where there was a duplicated key value. (Bug #46675, Bug #11754979) * Upgrades using an RPM package recreated the test database, which is undesirable when the DBA had removed it. (Bug #45415, Bug #11753896) -- Daniel Fischer, Release Staff Engineer, MySQL RE 49,8.37 +491704447185 ORACLE Deutschland B.V. & Co. KG, Riesstr. 25, 80992 München - HRA MUC 95603 Komplementaer: ORACLE Deutschl. Verw. B.V., Rijnzathe 6, 3454PV De Meern, NL Geschaeftsfuehrer: Juergen Kunz, Marcel van de Molen, Alexander van der Ven -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL 5.5.3-m3 and MyQL 5.5.4-m4 have been released
CALL Statements." + The CLIENT_MULTI_RESULTS flag now is enabled by default. It no longer needs to be enabled when you call mysql_real_connect(). (This flag is necessary for executing stored procedures because they can produce multiple result sets.) For PREPARE and EXECUTE, placeholder support for OUT and INOUT parameters is now available. See Section 12.2.1, "CALL Syntax." (Bug#11638: http://bugs.mysql.com/bug.php?id=11638, Bug#17898: http://bugs.mysql.com/bug.php?id=17898) * Three options were added to mysqldump make it easier to generate a dump from a slave server: + --dump-slave is similar to --master-data, but the CHANGE MASTER TO statement contains binary log coordinates for the slave's master host, not the slave itself. + --apply-slave-statements causes STOP SLAVE and START SLAVE statements to be added before the CHANGE MASTER TO statement and at the end of the output, respectively. + --include-master-host-port causes the CHANGE MASTER TO statement to include MASTER_PORT and MASTER_HOST options for the slave's master. (Bug#8368: http://bugs.mysql.com/bug.php?id=8368) * mysqladmin now allows the password value to be omitted following the password command. In this case, mysqladmin prompts for the password value, which enables you to avoid specifying the password on the command line. Omitting the password value should be done only if password is the final command on the mysqladmin command line. Otherwise, the next argument is taken as the password. (Bug#5724: http://bugs.mysql.com/bug.php?id=5724) * The server now provides a pluggable audit interface that enables information about server operations to be reported to interested parties. Audit plugins may register with the audit interface to receive notification about server operations. When an auditable event occurs within the server, the server determines whether notification is needed. For each registered audit plugin, the server checks the event against those event classes in which the plugin is interested and passes the event to the plugin if there is a match. For more information, see Section 22.2.3.3, "Audit Plugins." * Some conversions between Japanese character sets are more efficient. * When the server detects MyISAM table corruption, it now writes additional information to the error log, such as the name and line number of the source file, and the list of threads accessing the table. Example: Got an error from thread_id=1, mi_dynrec.c:368. This is useful information to include in bug reports. * The TABLESPACES table has been added to INFORMATION_SCHEMA for tracking tablespace details. * Added the PARAMETERS table to INFORMATION_SCHEMA. The PARAMETERS table provides information about stored function and procedure parameters, and about return values for stored functions. * The maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters. Bugs fixed: If you see this text instead of a list of actual fixes, you are receiving this message through one of our lists that limits message length to 5 bytes. Please refer to the web version of the changelog for a full list of fixes: http://dev.mysql.com/doc/refman/5.5/en/news-5-5-3.html -- Daniel Fischer, MySQL Tech Lead Build+49 170 4447185 Sun Microsystems GmbH, Sonnenallee 1, DE-85551 Kirchheim-Heimstetten Geschaeftsfuehrer: Juergen Kunz HRB MUC 161028 49.011, 8.376 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
MySQL Community Server 5.0.81 has been released
o enable the MySQL distribution to compile on Microsoft Visual C++ Express 2008. (Bug#33907: http://bugs.mysql.com/33907) * The mysql client incorrectly parsed statements containing the word "delimiter" in mid-statement. This fix is different from the one applied for this bug in MySQL 5.0.66. (Bug#33812: http://bugs.mysql.com/33812) See also Bug#38158: http://bugs.mysql.com/38158. * For a stored procedure containing a SELECT * ... RIGHT JOIN query, execution failed for the second call. (Bug#33811: http://bugs.mysql.com/33811) * Previously, use of index hints with views (which do not have indexes) produced the error ERROR 1221 (HY000): Incorrect usage of USE/IGNORE INDEX and VIEW. Now this produces ERROR 1176 (HY000): Key '...' doesn't exist in table '...', the same error as for base tables without an appropriate index. (Bug#33461: http://bugs.mysql.com/33461) * Cached queries that used 256 or more tables were not properly cached, so that later query invalidation due to a TRUNCATE TABLE for one of the tables caused the server to hang. (Bug#33362: http://bugs.mysql.com/33362) * Some division operations produced a result with incorrect precision. (Bug#31616: http://bugs.mysql.com/31616) * mysql_upgrade attempted to use the /proc file system even on systems that do not have it. (Bug#31605: http://bugs.mysql.com/31605) * mysqldump could fail to dump views containing a large number of columns. (Bug#31434: http://bugs.mysql.com/31434) * Queries executed using join buffering of BIT columns could produce incorrect results. (Bug#31399: http://bugs.mysql.com/31399) * ALTER TABLE CONVERT TO CHARACTER SET did not convert TINYTEXT or MEDIUMTEXT columns to a longer text type if necessary when converting the column to a different character set. (Bug#31291: http://bugs.mysql.com/31291) * For installation on Solaris using pkgadd packages, the mysql_install_db script was generated in the scripts directory, but the temporary files used during the process were left there and not deleted. (Bug#31052: http://bugs.mysql.com/31052) * Several MySQL programs could fail if the HOME environment variable had an empty value. (Bug#30394: http://bugs.mysql.com/30394) * On NetWare, mysql_install_db could appear to execute normally even if it failed to create the initial databases. (Bug#30129: http://bugs.mysql.com/30129) * The Serbian translation for the ER_INCORRECT_GLOBAL_LOCAL_VAR error was corrected. (Bug#29738: http://bugs.mysql.com/29738) * XA transaction rollbacks could result in corrupted transaction states and a server crash. (Bug#28323: http://bugs.mysql.com/28323) * The BUILD/check-cpu build script failed if gcc had a different name (such as gcc.real on Debian). (Bug#27526: http://bugs.mysql.com/27526) * On Windows, Visual Studio does not take into account some x86 hardware limitations, which led to incorrect results converting large DOUBLE values to unsigned BIGINT values. (Bug#27483: http://bugs.mysql.com/27483) * SSL support was not included in some "generic" RPM packages. (Bug#26760: http://bugs.mysql.com/26760) * In some cases, the parser interpreted the ; character as the end of input and misinterpreted stored program definitions. (Bug#26030: http://bugs.mysql.com/26030) * The Questions status variable is intended as a count of statements sent by clients to the server, but was also counting statements executed within stored routines. (Bug#24289: http://bugs.mysql.com/24289) * For access to the INFORMATION_SCHEMA.VIEWS table, the server did not check the SHOW VIEW and SELECT privileges, leading to inconsistency between output from that table and the SHOW CREATE VIEW statement. (Bug#22763: http://bugs.mysql.com/22763) * The FLUSH PRIVILEGES statement did not produce an error when it failed. (Bug#21226: http://bugs.mysql.com/21226) * A race condition between the mysqld.exe server and the Windows service manager could lead to inability to stop the server from the service manager. (Bug#20430: http://bugs.mysql.com/20430) * mysqld_safe would sometimes fail to remove the pid file for the old mysql process after a crash. As a result, the server would fail to start due to a false A mysqld process already exists... error. (Bug#11122: http://bugs.mysql.com/11122) Enjoy, Daniel -- Daniel Fischer, MySQL Tech Lead Build +46 18174400 ext. 4537 Sun Microsystems GmbHSonnenallee 1, DE-85551 Kirchheim-Heimstetten Geschaeftsfuehr
