Strange error with text concatention UTF8+win1250

[Dzyszla]

I have two selects:

SELECT 'u' || CAST('Kwota faktury płatna wyłącznie na rachunek ING Commercial Finance Polska S.A.,
ul. Malczewskiego 45, 02-622 Warszawa, www.ingcomfin.pl
Bank: ING Bank Śląski
rachunek nr: PL33 1050 0099 5381 0000 1000 9471
któremu zbyliśmy nasze wierzytelności łącznie z niniejszą.' AS BLOB CHARACTER SET win1250)
FROM rdb$database

SELECT 'u' || CAST(' Kwota faktury płatna wyłącznie na rachunek ING Commercial Finance Polska S.A.,
ul. Malczewskiego 45, 02-622 Warszawa, www.ingcomfin.pl
Bank: ING Bank Śląski
rachunek nr: PL33 1050 0099 5381 0000 1000 9471
któremu zbyliśmy nasze wierzytelności łącznie z niniejszą.' AS BLOB CHARACTER SET win1250)
FROM rdb$database

execute on connection UTF8.
FB 3.0.12

First not working, second (add space in casting string) working. Something else changed - working.

What's wrong?

[mrotteveel]

What is the error?

[Dzyszla]

Cannot transliterate character between character sets.

[Dzyszla]

Affected on 4.0.5 too.

[mrotteveel]

I can reproduce it (tried with DBeaver), but I have no clue why.

[mrotteveel]

Also on 5.0.1

[Dzyszla]

Workaround (I think) for now - make explicit cast second field on utf8 (after cast as win1250 - in fact, this query simulates a database field that is in this encoding):

SELECT 'u' || CAST(CAST('Kwota faktury płatna wyłącznie na rachunek ING Commercial Finance Polska S.A.,
ul. Malczewskiego 45, 02-622 Warszawa, www.ingcomfin.pl
Bank: ING Bank Śląski
rachunek nr: PL33 1050 0099 5381 0000 1000 9471
któremu zbyliśmy nasze wierzytelności łącznie z niniejszą.' AS BLOB SUB_TYPE text CHARACTER SET win1250) AS BLOB SUB_TYPE text CHARACTER SET utf8)
FROM rdb$database

[asfernandes]

I'm already debuging it and found where the problem is. The problem is highly dependent on the blob content where the WIN1250 character is a multibyte character in UTF8 and cannot be fit in the converted buffer.

[Dzyszla]

I hope it is fixable. :) Are you planning to fix it in v. 3?

[asfernandes]

I hope it is fixable. :) Are you planning to fix it in v. 3?

I hope so, but we need to take care, it's complicated routine with the bug there much probably for decades.