Jaybird 2.1.6

Jaybird 2.1.6 released, with the following fixes:

• JDBC-97: Blob.getBytes() method should not allow position below 1 — not critical
• JDBC-108: Problems with record result set to call primary composite — critical
• JDBC-119: updateRow() primary key violation issue — critical
• JDBC-118: Remote PID and process name for FB 2.1 monitoring tables — not critical

Comments to JDBC-118:

The only platform independent solution turns out to be via the -D property, therefore two new properties are implemented: org.firebirdsql.jdbc.pid and org.firebirdsql.jdbc.processName. If they are specified, values are passed to Firebird 2.1. Also one can use "normal" properties passed via URL or data source configuration. In this case, the property names are process_id and process_name.

With versions of Firebird prior to FB 2.1, using these properties will cause an exception while connecting to Firebird. A more intelligent solution will be implemented in Jaybird 2.2.

Jaybird 2.1.5

What’s new in Jaybird 2.1.5:

• Bugfix for events support on Linux

Jaybird 2.1.4

What’s new in Jaybird 2.1.4:

• support for events for Firebird 2.1
• new JNI code supporting multiple client libraries
• new property allowing to change the default result set holdability
• Feature #1428474. Implement record and tablename functionality from gstat
• Improved performance of ResultSet.getBytes() method for BLOB columns

Jaybird 2.1.3

Changes in Jaybird 2.1.3

• Firebird 2.1 compatibility updates

Jaybird 2.1.2

Bugs fixed in Jaybird 2.1.2

• JDBC-106 When table name contains lower case letters, metadata information about table columns is not returned from the driver.

Jaybird 2.1.1

Bugs fixed in Jaybird 2.1.1

• JDBC-100 When using the FBDatabaseMetaData.getColumns() method to check whether a column is nullable or not, the method will return wrong values for columns, which are defined by a domain.
• Fixed issue with DatabaseMetaData result sets, when underlying statements were not closed when connection was closed and caused errors during garbage collection.
• Support for INSERT...RETURNING statements.
• JDK 6.0 compatibility.

Jaybird 2.1.0

Bugs fixed in Jaybird 2.1.0

• JDBC-92. DatabaseMetaData becomes unusable when the statement that serves the result set is closed.
• JDBC-87. Backported feature of upcoming Jaybird 2.2 release that allows specifying the octetsAsBytes connection property and receive byte[] when using the ResultSet.getObject() method
• JDBC-85. Fixed returning of the error messages.
• Bug reported in Firebird-Java group. ClassCastException when obtaining byte[] from BLOB fields in cached result set.

Jaybird 2.1.0-RC-1

Jaybird_2_1_0_RC1

This commit was manufactured by cvs2svn to create tag 'Jaybird_2_1_0_…

Jaybird 2.1.0-beta-1

Jaybird_2_1_0_beta1

This commit was manufactured by cvs2svn to create tag 'Jaybird_2_1_0_…

JayBird 2.0.1

Bugs fixed in JayBird 2.0.1

• #1421579. Wrong result with Dialect 3 and FBDatabaseMetaData.getIndexInfo
• #1434183. Error from verifier on deploying JayBird as resource adapter
• #1449499. Incorrect DECIMAL_DIGITS value
• #1460163. “Could not obtain connection” hides original exception
• #1464522. JayBird: batch execution doesn’t work with blob columns
• #1464795. getCrossReference returns wrong FK Column/Table Name
• #1067485. Data truncation when use PreparedStatement in CHAR fields
• Issue reported in this group that it is not possible to access databases with paths that contain accented characters in embedded mode
• Changes to the encoding handling framework that should improve memory usage in the application.