Functionality added or changed:
          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 completly
          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)
        
Bugs fixed:
          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)
        
          On AMD64, attempting to repair a MyISAM
          table with a full-text index 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
          
          syntax. (Bug#10407)
        database_name.table_name
          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)
        
Ésta es una traducción del manual de referencia de MySQL, que puede encontrarse en dev.mysql.com. El manual de referencia original de MySQL está escrito en inglés, y esta traducción no necesariamente está tan actualizada como la versión original. Para cualquier sugerencia sobre la traducción y para señalar errores de cualquier tipo, no dude en dirigirse a mysql-es@vespito.com.

