Jaybird 3.0.2
The following has been changed or fixed since Jaybird 3.0.1
- Fixed: Specifying an unknown Java character set in connection property
charSetorlocalEncodingwas handled as if no connection character set had been specified, now we throw an exception that the character set is unknown. (JDBC-498) - Changed: Specifying a connection character set is no longer required, and will now default to
NONEagain, if system propertyorg.firebirdsql.jdbc.defaultConnectionEncodingis not specified. (JDBC-502)
The new requirement turned out to be too restrictive and hindering adoption of Jaybird 3. If you do want strict behaviour, you can specify system propertyorg.firebirdsql.jdbc.requireConnectionEncodingwith valuetrue.
See the full release notes for more information.
The release is also available on maven(*):
<groupId>org.firebirdsql.jdbc</groupId>
<artifactId>jaybird-jdkXX</artifactId>
<version>3.0.2</version>
* The artifactId depends on your target Java version: jaybird-jdk18, or jaybird-jdk17