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
Charset transliterations don't work with EXECUTE STATEMENT [CORE1331] #1750
Comments
Modified by: @asfernandesVersion: 2.1 Alpha 1 [ 10150 ] Version: 1.5.4 [ 10100 ] Version: 1.5.3 [ 10028 ] Version: 1.5.2 [ 10027 ] Version: 2.1 Beta 1 [ 10141 ] Version: 2.0.2 [ 10130 ] Fix Version: 2.1 Beta 2 [ 10190 ] Component: Engine [ 10000 ] |
Modified by: @asfernandesassignee: Adriano dos Santos Fernandes [ asfernandes ] |
Modified by: @pcisarAttachment: baza.fdb.gz [ 10430 ] |
Modified by: @pcisardescription: I have a database where all columns are UTF8. I have data in it in Russian Cyrillic characters. The client connects using WIN1251 charset and reads/writes values without any problems. However, when it tries to do the same with EXECUTE STATEMENT it gets error message about transliteration. The sample database file (with one table and two rows) can be found at: or gzipped: Here are 3 queries. When connected with charset UTF8, all queries work. When connected with WIN1251, first two queries work, but the third one fails: 1. This works: select opis from T1; 2. This works: set term !! ; 3. This fails: set term !! ; With error: arithmetic exception, numeric overflow, or string truncation Cannot => I have a database where all columns are UTF8. I have data in it in Russian Cyrillic characters. The client connects using WIN1251 charset and reads/writes values without any problems. However, when it tries to do the same with EXECUTE STATEMENT it gets error message about transliteration. The sample database file (with one table and two rows) is attached. Here are 3 queries. When connected with charset UTF8, all queries work. When connected with WIN1251, first two queries work, but the third one fails: 1. This works: select opis from T1; 2. This works: set term !! ; 3. This fails: set term !! ; With error: arithmetic exception, numeric overflow, or string truncation Cannot |
Modified by: @asfernandesFix Version: 2.0.2 [ 10130 ] |
Modified by: @pcisarVersion: 2.0.2 [ 10130 ] => |
Commented by: @pcisar Verified, test added. |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pcisarWorkflow: jira [ 12420 ] => Firebird [ 14912 ] |
Modified by: @pavel-zotovQA Status: No test |
Modified by: @pavel-zotovQA Status: No test => Done successfully |
Submitted by: Milan Babuskov (babuskov)
Is related to QA169
Attachments:
baza.fdb.gz
I have a database where all columns are UTF8. I have data in it in Russian Cyrillic characters. The client connects using WIN1251 charset and reads/writes values without any problems. However, when it tries to do the same with EXECUTE STATEMENT it gets error message about transliteration.
The sample database file (with one table and two rows) is attached.
Here are 3 queries. When connected with charset UTF8, all queries work. When connected with WIN1251, first two queries work, but the third one fails:
1. This works:
select opis from T1;
2. This works:
set term !! ;
execute block returns ( opis varchar(100) ) as
BEGIN
for select opis from t1 into :opis
do SUSPEND;
END!!
3. This fails:
set term !! ;
execute block returns ( opis varchar(100) ) as
BEGIN
for execute statement 'select opis from t1'
into :opis
do SUSPEND;
END!!
With error:
arithmetic exception, numeric overflow, or string truncation Cannot
transliterate character between character sets.
Commits: 3cb8f94 81f1f81
The text was updated successfully, but these errors were encountered: