|
From: Adriano d. S. F. <adr...@gm...> - 2009-08-26 15:21:09
|
Dmitry Yemanov escreveu: > Douglas Tosi wrote: > >> I'm investigating an obscure bug where a client accessing >> mon$statement is receiving an "invalid BLOB ID" error. >> > > Hmmmm. It should be "malformed string", actually. > > >> This happens only when there are statements submitted by clients using >> charset NONE. >> > > And passing non-ASCII strings inside SQL statements? > > This is expected. With NONE, the engine has no idea what charset has the > SQL text passed from the client. But it has to write it into the UNICODE > column MON$SQL_TEXT. During copying, the value is verified to be > well-formed from the destination charset point of view, thus the error > is thrown. What do you think of replacing mon$sql_text non-ascii chars done with NONE charset by question mark? Also, there is the introducer syntax with mix characters, AFAIR nobody objected to translate them to hex strings. Adriano |