|Subject||Re: [firebird-support] Invalid Blob ID and Charset|
> Thanks Vlad, but tell me:Engine will be able to convert ASCII characters into UTF8 when populated
> 1. What are the implications of connecting to a DB with CHARSET ASCII when
> it was created with Charset NONE?
monitoring tables. It is impossible to convert NONE into the any other encoding.
> 2. This tracker issue doesn't mention invalid Blob ID. The failureIIRC, some people have "invalid blob id" error before this was fixed.
> mentioned... how does it present itself if it is not invalid BLOB ID?
> 3. I have tested now by changing the application to connect with charsetGood
> ASCII and the monitor application also uses ACSCII, there is now no
> exception raised.
> But I have no knowledge of whether non ascii charactersI have no full details about this case. Probably Adriano or Dmitry know more.
> are ever placed in the MON$tables. The user name.... all security DBs have
> UNICODE_FSS as the username charset and these values are indeed going into
> the MON$ tables, I have no control over that. What are the implications of
> connecting via charset ASCII and having UNICODE_FSS characters going into
> MON$ tables? Will this cause MON$ table read failures?
AFAIU, issue not with data stored in database (such as user names, etc) but with data
supplied by user at run-time such as queries text's, connection string, etc.
Note, ASCII characters have the same representation in the UTF8. So i guess when
string in NONE encoding interpreted as UTF8 string it will fail only if it contain non-ASCII