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
Jaybird 3.0 introduced the requirement for a connection character set being explicitly specified (JDBC446). 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).
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
Submitted by: @mrotteveel
Relate to JDBC446
Replaces JDBC479
Jaybird 3.0 introduced the requirement for a connection character set being explicitly specified (JDBC446). 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).
Commits: 0e484bd a708a02
The text was updated successfully, but these errors were encountered: