MySQL Bugs: #10348: Can't initialize character set INSERT'ing BLOB if size > "max_allowed

Bug #10348	Can't initialize character set INSERT'ing BLOB if size > "max_allowed_packet"
Submitted:	3 May 2005 20:52	Modified:	22 May 2007 1:27
Reporter:	Dmitry Mironov	Email Updates:
Status:	Unsupported	Impact on me:	None
Category:	Connector / ODBC	Severity:	S1 (Critical)
Version:	3.51	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
When sending BLOB's of size bigger than "max_allowed_packet",
it says "Can't initialize character set .."

this connection becomes unusable, needs to reconnect.

saving blobs here ..
.. 
*** BLOB SIZE IS 1048576
TORTURE COMPLAINED with Can't initialize character set cp1251 (path: C:\mysql\\share\charsets\): size 1048576

sql_query "SHOW DATABASES"
SQL QUERY ERROR: SHOW DATABASES
SQL QUERY ERROR: Can't initialize character set cp1251 (path: C:\mysql\\share\charsets\)

How to repeat:
Reproduce:

1. Create binary data of size 131072, 262144, 524288 bytes, so on.
2. Do "INSERT INTO `db`.`table` (`blob`) VALUES (`mysql_real_escape_string your string`)"

*** BLOB SIZE IS 131072
Connecting to the database
Make initial setup queries
Database etlwarehouse is now connected
......
*** BLOB SIZE IS 1048576
TORTURE COMPLAINED with Can't initialize character set cp1251 (path: C:\mysql\\share\charsets\): size 1048576

ODBC bug script (Tcl, for general idea)

Attachment: torture.tcl (application/octet-stream, text), 1.49 KiB.

Console snapshot

Attachment: torture.jpg (image/pjpeg, text), 68.45 KiB.

Hi!

Could you please upload your test-case app that reproduces this behaviour ?

Thanks a lot.

The bug was transfered to developer.

This bug doesn't have anything to do with Connector/ODBC. The example code appears to use the mysqltcl interface, which we do not provide support for.

You can find out more about mysqltcl, including how to contact its authors, at http://www.xdobry.de/mysqltcl/