Attachments using NONE charset may cause reads from MON$ tables to fail [CORE2602] #3012
Submitted by: @asfernandes
When an attachment using NONE charset uses non-ASCII characters that go to MON$ tables, selects from MON$ tables (in other attachments) fail.
The error is about incorrect transliteration (v2.1.X) or malformed string (v2.5).
The problem is that with NONE there is no way to convert strings from unknown charset to system charset, that will be converted later to client charset.
The solution for this problem is to replace (only with attachments using NONE) non-ASCII characters that go to MON$ to question marks.
The text was updated successfully, but these errors were encountered: