Fixes bugs found since release 5.1.16.
LIKE was not optimized in then
server when run against
tables and no wildcards were used. Databases/tables with
'%' in their names
(escaped or not) are handled by this code path, although slower,
since it is rare to find these characters in table names in SQL.
If there is a
in the string,
LIKE takes care of
'=' is now used instead. The
only exception is the
database, which is handled separately. The patch covers both
The first call to a stored procedure failed with “No
Database Selected”. The workaround introduced in
fix the server bug where
PROCEDURE was not respecting lowercase table names was
misbehaving when the connection was not attached to a database
and on case-insensitive operating systems.
There was a concurrency bottleneck in Java's character set
encoding/decoding when converting bytes to/from
No longer use
new String(byte...). Use the
StringUtils method instead.
Connector/J now avoids a concurrent bottleneck in Java's
character set encoding/decoding when converting bytes to and
from instances of
(Bug #61105, Bug #12622056)