|
From: Dmitry Y. <fir...@ya...> - 2009-08-26 14:46:20
|
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. Dmitry |