Oops.
Jim White wrote:
Lam King Tin wrote:
...
SQL Exception: Unsupported character encoding 'ISO8859_1'.
...
...
kaffe-1.0.6/libraries/javalib/kaffe/io/CharToByteConverter.java
private static CharToByteConverter getConverterInternal(String enc)
{
...
String realenc = encodingRoot +
Dear Jim,
Deep thanks for your debugging.
But I do see the 7th alias should match, am I right?
That is: alias.put("ISO8859_1","8859_1");
So I still can't understand why this error comes out.
Best regards,
King Tin
Quoting Jim White <[EMAIL PROTECTED]>:
> Lam King Tin wrote:
>
Lam King Tin wrote:
Dear Jim,
Thank you very much for your reply.
I have tried to replace the method with the fixed version from Connector/J 5.0
as follows. The casting exception has disappeared. However, now I always
encounter below. This encoding should be the most common, right? But why
Dear Jim,
Thank you very much for your reply.
I have tried to replace the method with the fixed version from Connector/J 5.0
as follows. The casting exception has disappeared. However, now I always
encounter below. This encoding should be the most common, right? But why this
happens. Thanks.
Lam King Tin wrote:
...
SingleByteCharsetConverter converter = (SingleByteCharsetConverter)
this.charsetConverterMap.get(javaEncodingName);
Do you know what's the reason of the casting exception and any manageable
solution? Thank you very much.
Best regards,
King Tin
SQL Exception: Unab
Dear Dalibor,
I encountered a problem in using MySQL JDBC driver on JESSICA2 (Kaffe 1.0.6). I
believe this is a Kaffe problem. If this problem can be solved, then JESSICA2
can be operating with a backend MySQL cluster - a combination providing better
scalability with database applications.
T
