- [71621] MysqlXAConnection#xidToString(Xid xid) produces too much garbage
This one affects all applications which use XA transactions. Applying the patch attached to the issue avoids creation of a lot of garbage produced by converting Xid to a string when executing the XA commands.
- [71623] Field#getStringFromBytes() creates useless byte array when using JVM converter
When the JDBC driver uses JVM Charsets (e.g. you set useJvmCharsetConverters to true) to convert bytes representing the meta-data of a ResultSet into strings, the current implementation would create an useless byte array. The patch attached to the issue fixes this problem.
- [71672] Every SQL statement is checked if it contains "ON DUPLICATE KEY UPDATE" or not
The current implementation of server prepared statements (e.g. you set useServerPrepStmts to true) in Connector/J checks every SQL statement, whether it contains the clause "ON DUPLICATE KEY UPDATE" or not. But this clause is only valid for INSERT statements. The patch attached to the issue changes the code of Connector/J to perform this check only for INSERT statements and it adds also an option "avoidCheckOnDuplicateKeyUpdateInSQL", which is set to false per default, to disable the check even for INSERT statements, as not all applications make use of the "ON DUPLICATE KEY UPDATE" clause.
- [71679] Avoid iterator creation when invoking statement interceptors in MysqlIO
This is a minor change, which just avoids creation of an Iterator instance when executing statement interceptors.
Monday, February 17, 2014
Faster MySQL Connector/J
I have submitted 4 new patches to improve the performance of MySQL Connector/J:
So in case you want to improve the performance of your application and you don't want to wait, until Oracle releases a new version of MySQL Connector/J, then you should consider patching MySQL Connector/J using my patches.
Labels:
Connector/J,
Java,
JDBC,
MySQL,
performance,
XA
Subscribe to:
Posts (Atom)