Issue Details (XML | Word | Printable)

Key: CORE-2531
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dmitry Yemanov
Reporter: Dmitry Yemanov
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Firebird Core

The famous "cannot transliterate" error may be thrown when selecting data from the monitoring tables

Created: 26/Jun/09 08:39 PM   Updated: 16/Nov/09 05:36 PM
Component/s: Engine
Affects Version/s: 2.1.0, 2.5 Alpha 1, 2.1.1, 2.1.2, 2.5 Beta 1
Fix Version/s: 2.1.3

Time Tracking:
Not Specified

Issue Links:
Relate
 

Planning Status: Unspecified


 Description  « Hide
If any non-Unicode connection has some statements prepared and appropriate SQL text contains non-ASCII characters and the MON$ tables are queried in an Unicode connection, this error is thrown by any v2.1 version.

In v2.1.3 RC1, the situation is even worse: error may happen even if the MON$ tables are queried using the same attachment charset, provided that it's not Unicode. The patch to fix the regression and revert to the pre-v2.1.3 behavior is a trivial one-liner, but a complete fix is somewhat more difficult.

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Douglas Tosi added a comment - 26/Jun/09 08:51 PM
I've been hit by this on a number of occasions. What I do (and recommend my users to do) is use the same charset on the monitoring attachment and on other client attachments.
Unfortunately this is not always possible or desirable.

The complete fix would be most welcome.
Voted +1.

Dmitry Yemanov added a comment - 06/Jul/09 05:50 AM
The whole patch is to be backported into HEAD.