Kjell Rilbe escreveu:

> Milan Babuskov wrote:
>
>> FlameRobin transliterates the entire statement to the connection
>> character set (we do parse it to find identifiers for post-processing,
>> but we never alter the user-entered string).
>> =20
>> I never tried, but if system table columns are UTF8, I assume FB should
>> transliterate from connection charset to UTF8 when writing them.
>
> Interesting. The problem I had was this, in FlameRobin 0.8.6 with FB=20
> 2.1, both running on the same Windows 2000 setup with Windows 1252=20
> codepage (don't remember the connection charset, but I think it was=20
> ISO8859_1 or WINDOWS_1252):
>
> create table "Anv=E4ndare" (
> "L=F6senord" varchar(35) not null,
> constraint "Anv=E4ndareL=F6senordL=E4ngd"
> check (char_length("L=F6senord") >=3D 8)
> );
>
> This statement executes fine, but when I try to commit I get this error:
>
> ------------------------------------
> SQL Message : -104
> Invalid token
>
> Engine Code : 335544343
> Engine Message :
> invalid request BLR at offset 16
> column L=F6senord is not defined in table Anv=C3=A4ndare
> ------------------------------------
>
> Note that "L=F6senord" appears correct in the message while "Anv=E4ndare"=20
> appears mangled.
>

Firebird still have problems with exceptions and metadata names using
non-ASCII characters.


Adriano