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
MON$DATABASE_NAME and MON$ATTACHMENT_NAME fields contain question marks instead of non-ASCII characters regardless of the connection charset [CORE3508] #3866
Comments
Modified by: @dyemanovassignee: Dmitry Yemanov [ dimitr ] |
Modified by: @dyemanovstatus: Open [ 1 ] => In Progress [ 3 ] |
Modified by: @dyemanovVersion: 3.0 Initial [ 10301 ] |
Modified by: @dyemanovstatus: In Progress [ 3 ] => Open [ 1 ] |
Modified by: @dyemanovstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5.1 [ 10333 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Commented by: @pavel-zotov Create following script:shell del C:\MIX\firebird\QA\fbt-repo\tmp\Ministère_des_Affaires_étrangères 2>nul; create database '/3333:C:\MIX\firebird\QA\fbt-repo\tmp\Министерство_иностранных_дел'; // Name of Ministry of Foreign Affairs in Russia select 'literal string' as source, 'Министерство_иностранных_дел' as non_ascii_name from rdb$database
|
Modified by: @pavel-zotovAttachment: c3508-non-readable-non-ascii-characters-in-mon-tables.zip [ 12880 ] |
Modified by: @pavel-zotovAttachment: c3508-utf-LINUX-screen.PNG [ 12881 ] |
Commented by: @pavel-zotov ... and no any problem on Linux, database with non-ascii characters in its name is displayed properly - see attached .png. |
Submitted by: @dyemanov
Is related to CORE2602
Attachments:
c3508-non-readable-non-ascii-characters-in-mon-tables.zip
c3508-utf-LINUX-screen.PNG
If the database name or alias contain non-ASCII characters, they get replaced with question marks in the monitoring tables. Accordingly to CORE2602, it could be expected for the NONE connection charset, but in fact it happens for any charset, including Unicode ones.
Commits: be635fd 17be2f2
The text was updated successfully, but these errors were encountered: