Subject Re: UNICODE_FSS, internationalization issue
Author Panagiotis Konstantinidis
--- In, "Roman Rokytskyy"
<rrokytskyy@a...> wrote:
> > No, I'm already using PreparedStatements, that is I use the
> > family of methods to set data for the query.
> Then it should not happen. Can you prepare a standalone test case
> reproduces this problem? You can extend
> org.firebirdsql.jdbc.TestFBEncodings test case (it already contains
> tests for WIN1251, WIN1252, and UNICODE_FSS encodings.

Well now I'm really getting desperate... As if all the previous was
not enough I noticed that select queries with LIKE, containing
characters not included in the 8859_1 charset hang the database
connection utilizing all cpu.... I do not use any extraordinary
query.. Just a "SELECT * FROM table_name WHERE column_name
LIKE 'some unicode chars here'"

As before the file.encoding in JVM is in 8859_7. If I change that to
UTF-8 it works ok.

How does file.encoding effects the driver??? file.encoding should
not affect driver since I have explicitly set character set in the
database and in the jdbc connection...