Can you capture/log the exact
SQL query when the
exception happen ?
I am sorry, can't understand the
exception !, is it a fail to find parameter or something, like the there is
SQL but broken !?
Anyway, i suspect the use of RawByteString is and as always the root of evil, so i will adjust your code a little to remove this dependency as much as i can.
ps: i asked for specific test vector to guarantee the migration of your code, and you didn't answer with one specific value, the one with strange
Unicode would be helpful, yet from my understanding it is working fine, mostly !,
again does the
exception due to broken/corrupted
SQL or truncated
SQL.... only after that we can guess if some combination of
Unicode chars lost.
More details will remove the guessing game, and only you can get these details.