MySQL Bugs: #20208: Blobs greater than 8K are being truncated to 8K

Bug #20208	Blobs greater than 8K are being truncated to 8K
Submitted:	1 Jun 2006 15:36	Modified:	11 Jan 2013 12:24
Reporter:	Curtis Beattie	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / ODBC	Severity:	S2 (Serious)
Version:	3.51.20, 5.1alpha	OS:	Any
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any

File:	Maximum allowed size is 50MB.
Description:
Privacy:

If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.

To split a large file:

On *nix platforms use the split command e.g. split -b 50MB <my_large_archive> <my_split_archive_prefix>
On windows use WinZip or a similar utility to split the large file

Test case uses MySQL C API shows that UNCOMPRESS function returns MYSQL_TYPE_VAR_STRING result for both BLOB and VARCHAR

Attachment: mysql-list-fields-test.c (text/x-csrc), 2.46 KiB.

patch to fix SQLTables issue

Attachment: bug20208.diff (application/octet-stream, text), 2.63 KiB.

Update of the bugfix for SQLTables issue

Attachment: utility.diff (application/octet-stream, text), 2.64 KiB.