Skip to content

A quick summary of patch contributions included in MySQL 5.5

Posted by Lenz Grimmer on

I've been going through our bugs database to compile a list of some noteworthy patch contributions that have been included in the MySQL 5.5 release. Of course any contribution is appreciated, no matter how small! And the list is probably not complete — please let me know if I'm missing any. I omitted a number of smaller patches that fixed compile issues and I only considered contributions that were tracked in our bug database and were tagged as "Contribution".

Note that these are new patches that have not been part of any other MySQL release — of course, all contributions from previous releases are included in 5.5 as well. We also received a few patches for InnoDB (particularly by Mark Callaghan and his team mates at Google/Facebook), which were incorporated in the InnoDB plugin in MySQL 5.1 (and hence got included in the InnoDB version of MySQL 5.5, too).

Here they are, in no particular order:

  • BUG#13175: SHA2 function (Patch contributed by Bill Karwin)
  • BUG#14104: FLUSH LOGS now takes an optional log_type value so that FLUSH log_type LOGS can be used to flush only a specified log type. (Patch contributed by Eric Bergen)
  • BUG#27249: Aliases for wildcards (as in SELECT t.* AS 'alias' FROM t) are no longer accepted and result in an error. Previously, such aliases were ignored silently. (Patch contributed by Martin Friebe)
  • BUG#40368: mysqld_safe did not honor underscores in the same way as dashes for server options (Patch contributed by Erik Ljungstrom)
  • BUG#45767: Removal of Field::pack_key, Field::unpack_key, Field::pack_cmp storage engine functions (Patch contributed by Zardosht Kasheff)
  • BUG#50057: SHOW PROFILE CPU port for Windows (Patch contributed by Alex Budkovski)
  • BUG#5724: "mysqladmin password" prompts for a password when none is provided on the command line (Patch contributed by Harrison Fisk)
  • BUG#26780: A new mysql client option "--auto-vertical-output", which causes the client to test whether a result table is too wide for the current window (where available) and emit vertical results in that case. (Patch contributed by Eric Bergen)
A big "Thank you" to all the contributors!

Trackbacks

Comments

Display comments as Linear | Threaded

No comments

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
HTML-Tags will be converted to Entities.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA

Form options
tweetbackcheck