-
-
Notifications
You must be signed in to change notification settings - Fork 233
Operations with MON$STATEMENTS throw "cannot transliterate" error [CORE1358] #1776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Commented by: PAscal (legrand_legrand_63) when trying the folowing statement in FB 2.1: is that normal ? |
Commented by: @asfernandes Dmitry, seems to be due to embedded null characters inside the string. |
Commented by: @asfernandes Pascal, you caused-me a lot of confusion. :-) Please next time open a new bug report, and doesn't comment a different bug on another. |
Commented by: @dyemanov Fixed, thanks. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 12591 ] => Firebird [ 14201 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: @dyemanov
The monitoring tables weren't adjusted to the BLOB metadata changes. The RDB$SQL_TEXT column is of FSS_UNICODE charset and hence it should transliterate the string-2-blob conversion properly.
Commits: 341df76
The text was updated successfully, but these errors were encountered: