MySQL 5.5.47

# Bugs Fixed
- InnoDB: Altering the letter case of a column introduced an inconsistency between the frm file and data dictionary resulting in a failed CREATE INDEX operation on the altered column.
- MySQL development RPM packages could fail to install if MySQL Connector/C development RPM packages were installed.
- Possible buffer overflow from incorrect use of strcpy() and sprintf() was corrected.
- MySQL RPM packages for RHEL5 failed to create the mysql system user.
- Concurrent FLUSH PRIVILEGES and REVOKE or GRANT statements could produce a small time window during which invalid memory access to proxy user information could occur, leading to a server exit.
- Starting the server with the query_alloc_block_size system variable set to certain negative values on a machine without enough memory could result in out-of-memory errors.
- Using UNINSTALL PLUGIN to uninstall the daemon_example plugin could cause a server exit.
- FLUSH DES_KEY_FILE failed to reload the DES key file.
- A server exit could occur for the second execution of a prepared statement for which an ORDER BY clause referred to a column position.
- Repeated execution of a prepared statement could cause a server exit if the default database was changed.
- Outer references do not work as arguments to MATCH(), but the server did not properly detect them. Now it does and raises an error.
- Valgrind errors were produced during row comparator setup.
- INSERT DELAYED could cause a server exit for tables partitioned with a character column as the key and for which the expression required a character set conversion.
- A server exit could occur when updating a view using an ALL comparison operator on a subquery that selects from an indexed column in the main table.
- When a fixed-width row was inserted into a MyISAM temporary table, the entire content of the record buffer was written to the table, including any trailing space contained in VARCHAR columns, the issue being that this trailing space could be uninitialized. This problem has been resolved by insuring that only the bytes actually used to store the VARCHAR (and none extra) are copied and inserted in such cases.
- Temporary MyISAM tables (unlike normal MyISAM tables) did not use the dynamic row format when they contained VARCHAR columns, resulting in larger temporary files (and more file I/O) than necessary.