Problems with COMMENT ON and strings using introducer (charset) [CORE2804] #3192
Comments
Modified by: @pcisarreporter: Pavel Cisar [ pcisar ] => Kovalenko Dmitry [ _dima_k_ ] security: Managers [ 10013 ] => |
Modified by: @dyemanovVersion: 3.0 Initial [ 10301 ] Fix Version: 2.5 RC2 [ 10372 ] Fix Version: 3.0 Alpha 1 [ 10331 ] Component: Engine [ 10000 ] assignee: Adriano dos Santos Fernandes [ asfernandes ] summary: The problems with [COMMENT ON table IS 'russian text'] and markers of charsets => Problems with COMMENT ON and strings using introducer (charset) |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: Done with caveats Test Details: Database 'core2804-ods11.fbk' was prepared with following statements: Unfortunatelly, I don`t know how to extract and check data in fbt_run using WIN1251 charset: |
|
Commented by: @ibprovider >Unfortunatelly, I don`t know how to extract and check data in fbt_run using WIN1251 charset select cast( cast(rf.rdb$description as BLOB SUB_TYPE TEXT CHARACTER SET WIN1251) as BLOB SUB_TYPE TEXT CHARACTER SET NONE) from rdb$relation_fields rf ? |
|
Commented by: @pavel-zotov 2 Kovalenko Dmitry: thanks, now all works fine. |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] Test Details: Database 'core2804-ods11.fbk' was prepared with following statements: Unfortunatelly, I don`t know how to extract and check data in fbt_run using WIN1251 charset: => Database 'core2804-ods11.fbk' was prepared with following statements: Connection charset can be either 'UTF8' or 'WIN1251' - it should works with the same result. |
Modified by: @pavel-zotovstatus: Closed [ 6 ] => Closed [ 6 ] QA Status: Done with caveats => Done successfully |
Submitted by: @ibprovider
Server Version 2.5.0.25856
------- TEST1
Connection with NONE charset
When I run the
comment on TABLE dual is _win1251 'russian text'
Server returns the "malformed string". Here 'russian text' in win1251 charset
When I run the
comment on TABLE dual is _unicode_fss 'russian text'
Server returns OK. Here 'russian text' in UNICODE_FSS charset
------- TEST2
Connection with WIN1251 charset
When I run the
comment on TABLE dual is _win1251 'russian text'
Server returns OK.
When I run the
comment on TABLE dual is _unicode_fss 'russian text in UTF8 charset'
Server returns OK. But writes in system table the text with wrong charset
Commits: 914ef4c d129eec
====== Test Details ======
Database 'core2804-ods11.fbk' was prepared with following statements:
recreate table test1(id int);
recreate table test2(id int);
commit;
comment on table test1 is _win1251 'win1251: <cyrillic text here encoded with win1251>';
comment on table test2 is _unicode_fss 'unicode_fss: <cyrillic text here encoded with UTF8>';
commit;
Connection charset can be either 'UTF8' or 'WIN1251' - it should works with the same result.
The text was updated successfully, but these errors were encountered: