Subject | Interclient 2.5 + charset |
---|---|
Author | mw |
Post date | 2002-10-02T09:54:27Z |
Hi,
is it possible in InterClient 2.5 to set the character set on connecting?
In the docs. it says for property key "charSet":
<<<<<<<
The character encoding for the connection. All SQL and character input data
will be sent to the database using the specified character encoding. All
output data and InterBase messages retrieved from the database will also
utilize the specified character encoding. InterClient messages do not
utilize charSet, but derive from the resource bundle in use which is based
on the locale-specific encoding of the client. The encoding specified must
match one of the supported IANA character encoding names detailed in the
CharacterEncodings class.
Extension, proposed for InterClient 2.0, not yet supported
The question is really: are there going to be any problems connecting etc.
to a interbase65 db created with character set ISO_8859_1 and where all char
colums are also chrset 8859_1 with collation DE_DE??
TIA.
Mark
is it possible in InterClient 2.5 to set the character set on connecting?
In the docs. it says for property key "charSet":
<<<<<<<
The character encoding for the connection. All SQL and character input data
will be sent to the database using the specified character encoding. All
output data and InterBase messages retrieved from the database will also
utilize the specified character encoding. InterClient messages do not
utilize charSet, but derive from the resource bundle in use which is based
on the locale-specific encoding of the client. The encoding specified must
match one of the supported IANA character encoding names detailed in the
CharacterEncodings class.
Extension, proposed for InterClient 2.0, not yet supported
>>>>>>>>The last line is what is worrying me :-(
The question is really: are there going to be any problems connecting etc.
to a interbase65 db created with character set ISO_8859_1 and where all char
colums are also chrset 8859_1 with collation DE_DE??
TIA.
Mark