Bug #34018 describe implications of connection escaping on "max_allowed_packet size"
Submitted: 23 Jan 2008 20:01 Modified: 5 Feb 2009 17:42
Reporter: Ralf Hauser Email Updates:
Status: Closed Impact on me:
None 
Category:Connector / J Documentation Severity:S4 (Feature request)
Version: OS:Any
Assigned to: Tony Bedford CPU Architecture:Any
Triage: D4 (Minor)

[23 Jan 2008 20:01] Ralf Hauser
Description:
as from the mail I got <<Please add a bug/feature request in the Documentation category:
http://bugs.mysql.com

Read our comment policy for further details:
  http://dev.mysql.com/doc/mysql/comment-policy.html

The original comment:

please add an entry for the "Packet too large for query" exception
(http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html#option_mysqld_max_allo...)

Watch out, even though the binary blob size you want to insert via jdbc is safely below the max_allowed_packet size, the hexEscapeBlock() in
com.mysql.jdbc.PreparedStatement.streamToBytes() may almost double the size!>>

How to repeat:
just try to insert a blob

Suggested fix:
describe the issue
[4 Jul 2008 14:54] MC Brown
Assigning to Tony
[5 Feb 2009 17:42] Tony Bedford
A note has been added to the common problems and solutions section of the Connector/J documentation. Thanks!