MySQL Community Edition is a freely downloadable version of the world's most popular open source database that is supported by an active community of open source developers and enthusiasts.
MySQL delivers enterprise features, including:
• Partitioning to improve performance and management of very large database environments
• Row-based/Hybrid Replication for improved replication security
• Event Scheduler to create and schedule jobs that perform various database tasks
• XPath Support
• Dynamic General/Slow Query Log
• Performance/Load Testing Utility (mysqlslap)
• Improved! Full Text Search (faster, new dev templates)
• Improved! Archive engine (better compression, more features)
• Improved! User session and problem SQL identification
• Improved! MySQL embedded library (libmysqld)
• Additional INFORMATION_SCHEMA objects
• Faster data import operations (parallel file load)
• ACID Transactions to build reliable and secure business critical applications
• Stored Procedures to improve developer productivity
• Triggers to enforce complex business rules at the database level
• Views to ensure sensitive information is not compromised
• Information Schema to provide easy access to metadata
• Pluggable Storage Engine Architecture for maximum flexibility
• Archive Storage Engine for historical and audit data
# Bugs Fixed
* Important Change: Replication: Setting an empty user in a CHANGE MASTER TO statement caused an invalid internal result and is no longer permitted. Trying to use MASTER_USER='' or setting MASTER_PASSWORD while leaving MASTER_USER unset causes the statement to fail with an error.
* Important Change: Replication: Moving the binary log file, relay log file, or both files to a new location, then restarting the server with a new value for --log-bin, --relay-log, or both, caused the server to abort on start. This was because the entries in the index file overrode the new location. In addition, paths were calculated relative to datadir (rather than to the --log-bin or --relay-log values). The fix for this problem means that, when the server reads an entry from the index file, it now checks whether the entry contains a relative path. If it does, the relative part of the path is replaced with the absolute path set using the --log-bin or --relay-log option. An absolute path remains unchanged; in such a case, the index must be edited manually to enable the new path or paths to be used.
* InnoDB Storage Engine: When doing a live downgrade from MySQL 5.6.4 or later, with innodb_page_size set to a value other than 16384, now the earlier MySQL version reports that the page size is incompatible with the older version, rather than crashing or displaying a “corruption” error.
* InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY statements for InnoDB tables from concurrent threads could cause a deadlock, particularly with the INSERT...ON DUPLICATE KEY UPDATE form. The fix avoids deadlocks caused by the same row being accessed by more than one transaction. Deadlocks could still occur when multiple rows are inserted and updated simultaneously by different transactions in inconsistent order; those types of deadlocks require the standard error handling on the application side, of re-trying the transaction.