Hi Alexey,
I have no doubt it works for you and as well as for so many other people
out there!
I bet JBoss is being used in multilanguage environment many times by
now. But that is only making
it harder for me to understand why it does not work in our case.
Yesterday, I realized that our query
Hi Alexey,
I have no doubt it works for you as well as it does for so many other
people out there!
I bet JBoss is being used in multilanguage environment many times by
now. But that is only making
it harder for me to understand why it does not work in our case.
Yesterday, I realized that our q
FROM A AS o WHERE o.name='"
+ name + "'", null));
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Milen Dyankov
> Sent: Tuesday, January 27, 2004 6:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBos
en Dyankov
> Sent: Tuesday, January 27, 2004 5:25 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] Problem when query contains
> international characters
>
>
> People please, is my question too complicated or too stupid ??
>
> I think I may be narro
People please, is my question too complicated or too stupid ??
I think I may be narrowed down it to this:
Somewhere in generated from "JBossQLParser.jjt" and/or "EJBQLParser.jjt"
files,
my string "ąężźćśłóń" = [261,281,380,378,263,347,322,243,324]
changes like it was converted to UTF-16 -
[1,
Rupp, Heiko wrote:
What database are using?
Some databases don't like utf-8 for example when support for it is not
especially compiled in.
We have tried with FireBird, MySQL, MSSQL2000 and currently we are
testing on Pervasive.
UTF8 works just fine with all of them.
UTF8 characters are stored
What database are using?
Some databases don't like utf-8 for example when support for it is not
especially compiled in.
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the b
Hi again,
Some new information regarding the problem I have described in my
previous mail.
It doesn't seem to be related to any particular JBoss version (tested
with the same result on 3.2.1, 3.2.2 and 3.2.3).
It doesn't seem to depend on the JVM version (tested with J2SDK
1.4.1_02 and 1.4.2_