MySQL Bugs: #50180: TinyInt(1) causes error with client cursor but not with server cursor

Bug #50180	TinyInt(1) causes error with client cursor but not with server cursor
Submitted:	8 Jan 2010 10:56	Modified:	19 Oct 2012 10:32
Reporter:	Bogdan Degtyariov	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	Connector / ODBC	Severity:	S3 (Non-critical)
Version:		OS:	Any
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any
Tags:	adUseClient, adUseServer, Automation type not supported in VBScript, boolean, TinyInt(1), type mismatch

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

ODBC Trace for the case with the error

Attachment: SQL_TEST_VB_ERROR.LOG (application/octet-stream, text), 62.02 KiB.

ODBC Trace for the case with no error

Attachment: SQL_TEST_VB_NO_ERROR.LOG (application/octet-stream, text), 62.02 KiB.