Subject | Re: Performance bug located and solved |
---|---|
Author | Roman Rokytskyy |
Post date | 2002-11-23T14:03:52Z |
Hi,
charset for connection (DPB value) is still NONE (see
ConnectionProperties.java). Maybe Borland is correct that we need to
use ISO8859_1 when converting strings to byte[] when lc_ctype
is "NONE". I will check this.
tried TestFBEncoding.java test case?
Regards,
Roman
> Read code in Connection.java in the following places.This is encoding used to convert strings to byte[] and back. Default
>
> private final static String defaultEncoding__ =
> CharacterEncodings._8859_1;
> Connection()....................
> addRequiredPropertiesAndSetConverters()........................
charset for connection (DPB value) is still NONE (see
ConnectionProperties.java). Maybe Borland is correct that we need to
use ISO8859_1 when converting strings to byte[] when lc_ctype
is "NONE". I will check this.
> I have run the internal tests for the following character sets andDid your database contain language specific characters? Have you
> there are not failures at all.
>
> 1.- Server WIN1252, Client not set
> 2.- Server WIN1252, Client ISO8859_1
> 3.- Server WIN1252, Client WIN1252
> 4.- Server NONE, Client WIN1252
> 5.- Server NONE, Client not set
tried TestFBEncoding.java test case?
Regards,
Roman