Hey Roman!

Thanks for looking into it! The problem is probably related to the
fact that it is impossible to use BLOBs inside stored procedures. Is
it possible to trigger an error at the prepareStatement method just
like the "? IS NULL" condition? I found it confusing that some queries
did work without failure and some didn't related to a PRIMARY KEY
index that was or wasn't there.

A workaround would probably be to use some sort of checksum to see if
there where changes inside BLOB fields. Does the blob_col LIKE ?
condition work like expected?

Best Regards,
Bullit Energy