|
If you were logged in you would be able to see more operations.
|
|
|
| Planning Status: |
Unspecified
|
|
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.
|
|
Description
|
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. |
Show » |
| The cvs commits can not be displayed for repository Firebird at the moment since the log has not yet been parsed. The log will be parsed the next time the VcsService runs. If you have administrators privileges you can hasten the next time the service will run in the service section of the Administration pages.
|
|
Bug
Resolved
Major
The famous "cannot transliterate" error may be thrown when selecting data from the monitoring tables
