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
Non-ASCII data in SEC$USERS is not read correctly [CORE4301] #4624
Comments
Commented by: @sim1984 Database create as CREATE DATABASE 'localhost/3051:TEST' |
Modified by: @sim1984description: User comment distorts non-ASCII characters c:\Program Files\Firebird\Firebird_3_0>chcp 1251 c:\Program Files\Firebird\Firebird_3_0>isql
=================
|
Modified by: Sean Leyne (seanleyne)summary: Comment for users and user attributes distorts non-ASCII characters => COMMENT ON USER with non-ASCII characters are not saved correctly |
Commented by: Sean Leyne (seanleyne) I don't agree that should have a "Major" priority. |
Modified by: @sim1984priority: Major [ 3 ] => Minor [ 4 ] |
Commented by: @sim1984 I agree. |
Commented by: @asfernandes They are saved correctly. They are not read correctly. |
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @asfernandesVersion: 3.0 Alpha 2 [ 10560 ] summary: COMMENT ON USER with non-ASCII characters are not saved correctly => Non-ASCII data in SEC$USERS is not read correctly |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 3.0 Beta 1 [ 10332 ] |
Commented by: @pavel-zotov How can it be explained that if: 1) create new database: $ /opt/fb30ss/bin/isql -q 2) and run script with only ASCII characters: drop user tmp$c4301a; -- then result is NULLs in the sec$description: SEC$USER_NAME TMP$C4301A SEC$USER_NAME TMP$C4301B -- ? PS. DefaultDbCachePages = 8K ExternalFileAccess = Restrict /var/db/fb30 LockMemSize = 64M MaxUserTraceLogSize = 99999 |
Commented by: @pavel-zotov Sorry for my previous stupid post, the reason was obvious: usage of UserManager = Legacy_UserManager in config. If run this test on standard firebird.conf than all OK: $ /opt/fb30ss/bin/isql -q SEC$USER_NAME DESCR
|
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Done with caveats Test Details: For test content of COMMENTS field firebird.conf should contain: UserManager = Srp. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] Test Specifics: [Custom configuration required] |
Commented by: @pcisar Test created. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @sim1984
Is related to QA584
User comment distorts non-ASCII characters
c:\Program Files\Firebird\Firebird_3_0>chcp 1251
Текущая кодовая страница: 1251
c:\Program Files\Firebird\Firebird_3_0>isql
Use CONNECT or CREATE DATABASE to specify a database
SQL> set names win1251;
SQL> connect 'localhost/3051:test' user 'sysdba' password 'masterkey';
Database: 'localhost/3051:test', User: sysdba
SQL> create table T1(id integer);
SQL> commit;
SQL> comment on table T1 is 'Моя таблица';
SQL> commit;
SQL> select r.rdb$description as descr
CON> from rdb$relations r
CON> where r.rdb$relation_name = 'T1';
=================
0:3
DESCR:
Моя таблица
SQL> create user user1 password '123';
SQL> commit;
SQL> comment on user user1 is 'Новый пользователь';
SQL> commit;
SQL> select u.sec$description as descr
CON> from sec$users u
CON> where u.sec$user_name = 'USER1';
=================
0:5
DESCR:
?????????? ????????????????????????
SQL> alter user user1 set tags(tag1='привет');
SQL> commit;
SQL> select * from sec$user_attributes;
SEC$USER_NAME SEC$KEY SEC$VALUE
=============================== =============================== ========================================================
USER1 TAG1 ????????????
Commits: 79c6b21 FirebirdSQL/fbt-repository@07fe6f6
====== Test Details ======
For test content of COMMENTS field firebird.conf should contain: UserManager = Srp.
Currently it is not so on test-running host, so it was decided to check only content of FIRST_NAME field which is available on any value of `UserManager` parameter.
The text was updated successfully, but these errors were encountered: