Bug #10859 | PacketTooBigException using PreparedStatement.setBinaryStream | ||
---|---|---|---|
Submitted: | 25 May 2005 13:06 | Modified: | 25 May 2005 13:46 |
Reporter: | James Lord | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 3.1.8a | OS: | Windows (Windows XP) |
Assigned to: | CPU Architecture: | Any |
[25 May 2005 13:06]
James Lord
[25 May 2005 13:46]
Mark Matthews
This is already fixed in Connector/J 3.1.9 (to be released later this week). See the nightly downloads of 3.1.x at http://downloads.mysql.com/snapshots.php (there's now a "blobSendChunkSize" configuration property one can use, the default is 1mb.)
[8 Jan 2008 3:46]
Ryan Golhar
This is bug occurs using mySQL 5.0 on Windows 2000 using the Connector/J 5.1.5 using exactly the same test code. It does not appear that setting the blobSendChunkSize property works. Setting the server property max_allowed_packet greater than the blob size works.
[8 Jan 2008 5:03]
Mark Matthews
"blobSendChunkSize" only applies to server-side prepared statements. They're not enabled by default in Connector/J 5.0.x or 5.1.x because of issues with the server-side implementation of them. Client-side prepared statements can not "stream" blobs to the server.