> This is rather strange because we can run some code when we're not
> even touching records that contain blobs. We haven't selected any
> records containing blobs.

Hmmm... I remember there was similar issue some time ago, but I think that
bug was already fixed. Are you able to provide a test case that at least
under some conditions reproduces this problem? There it was related to the
multi-threaded access to the same connection object.

If you are not selecting any record with the BLOB fields, then something is
mixed inside driver, so it thinks that some field is blob and interprets its
data as BLOB data.

Thanks!
Roman