Issue Details (XML | Word | Printable)

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

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

Drop requirement for connection character set on connect

Created: 25/Jun/17 12:51 PM   Updated: 19/Aug/17 10:25 AM
Component/s: JDBC driver
Affects Version/s: Jaybird 3.0.0, Jaybird 3.0.1
Fix Version/s: Jaybird 3.0.2, Jaybird 4

Issue Links:
Relate
 
Replace
 


 Description  « Hide
Jaybird 3.0 introduced the requirement for a connection character set being explicitly specified (JDBC-446). This turns out to be rather cumbersome for users. We should drop this requirement and revert to the old default of NONE, and instead allow the system property org.firebirdsql.jdbc.defaultConnectionEncoding to override this default.

For strictness, we could opt to define a value of REJECT (eg org.firebirdsql.jdbc.defaultConnectionEncoding=REJECT), or a separate property (eg org.firebirdsql.jdbc.requireConnectionEncoding=true).

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel added a comment - 22/Jul/17 04:17 PM
Implemented. Without an explicit connection character set, Jaybird will default to NONE again. The default can be overridden with system property org.firebirdsql.jdbc.defaultConnectionEncoding with a valid Firebird character set name as value. The explicit character set requirement can be enabled by specifying system property org.firebirdsql.jdbc.requireConnectionEncoding with value true