Issue Details (XML | Word | Printable)

Key: JDBC-267
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: fabianobonin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jaybird JCA/JDBC Driver

Not all Java ChatSet names/aliases are available

Created: 12/Aug/12 06:39 PM   Updated: 21/Feb/13 08:10 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.1.6, Jaybird 2.2
Fix Version/s: Jaybird 2.2.1, Jaybird 3.0

Time Tracking:
Not Specified

Issue Links:
Relate
 


 Description  « Hide
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), 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

 All   Comments   Work Log   Change History   Version Control   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 18/Aug/12 07:32 AM
Scheduled for 2.3, if it is easy to do I will also include it in 2.2.1

Mark Rotteveel added a comment - 19/Aug/12 12:03 PM
Commited change to trunk to address both this and JDBC-268. I do think it needs a little bit more polish before it can go to Jaybird 2.2.1 as well.