You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1) If i pass the value "windows-1252" to Jaybird in the "charSet" property, it
throws an exception during connection, because it doesn´t know this charset name. It expects "cp1252" instead.
2) When i pass a unknown charset name to Jaybird, it throws a RuntimeError,
instead of a SQLException error, what makes it "uncatcheable" in most cases,
unless the code is catching RuntimeException's, what is not usual.
About problem 1, according to Mark (http://tech.groups.yahoo.com/group/Firebird-Java/message/10752 (archive)), Jaybird took Java charset names from Java 1.3, but there was a change in Java 1.4, wich changed some charset names and/or aliases. So it would be nice to have the new names/aliases mapped.
Submitted by: fabianobonin (fabianobonin)
Relate to JDBC268
System.out.println(Charset.defaultCharset().name());
output: windows-1252
We have two problems here:
1) If i pass the value "windows-1252" to Jaybird in the "charSet" property, it
throws an exception during connection, because it doesn´t know this charset name. It expects "cp1252" instead.
2) When i pass a unknown charset name to Jaybird, it throws a RuntimeError,
instead of a SQLException error, what makes it "uncatcheable" in most cases,
unless the code is catching RuntimeException's, what is not usual.
About problem 1, according to Mark (http://tech.groups.yahoo.com/group/Firebird-Java/message/10752 (archive)), Jaybird took Java charset names from Java 1.3, but there was a change in Java 1.4, wich changed some charset names and/or aliases. So it would be nice to have the new names/aliases mapped.
Fabiano
Commits: ac20951 36f66f5
The text was updated successfully, but these errors were encountered: