Attachments using NONE charset may cause reads from MON$ tables to fail [CORE2602]

[firebird-automations]

Submitted by: @asfernandes

Is related to QA412
Relate to CORE3508

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.

Commits: 83dfc4a

[firebird-automations]

Modified by: @asfernandes

assignee: Adriano dos Santos Fernandes [ asfernandes ]

summary: Attachments using NONE charset may cause reads from MON$ tables fail => Attachments using NONE charset may cause reads from MON$ tables to fail

[firebird-automations]

Modified by: @asfernandes

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 2.5 RC1 [ 10362 ]

[firebird-automations]

Modified by: @pcisar

Link: This issue is related to QA412 [ QA412 ]

[firebird-automations]

Modified by: @dyemanov

Link: This issue relate to CORE3508 [ CORE3508 ]

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Commented by: @pcisar

Test added.

[firebird-automations]

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: Done successfully