Firebird Class 4 JCA-JDBC Driver Downloads | Jaybird 2.1.6 (Critical) |
| July 19, 2008 | Jaybird-2.1.6JDK_1.3.zip | 2.8 MB | Jaybird 2.1.6 for JDK 1.3, zip kit |
| July 19, 2008 | Jaybird-2.1.6JDK_1.4.zip | 3.1 MB | Jaybird 2.1.6 for JDK 1.4, zip kit |
| July 19, 2008 | Jaybird-2.1.6JDK_1.5.zip | 3.1 MB | Jaybird 2.1.6 for JDK 1.5, zip kit |
| July 19, 2008 | Jaybird-2.1.6JDK_1.6.zip | 3.1 MB | Jaybird 2.1.6 for JDK 1.6, zip kit |
| July 19, 2008 | Jaybird-2.1.6-src.zip | 5.6 MB | Jaybird 2.1.6 Sources, zip kit |
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 resultset 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.
Due to critical fixes in JDBC-108 and JDBC-119, everybody using Jaybird versions between 2.1.2 and 2.1.5 is advised to upgrade to this new version to avoid data corruption when doing updates via ResultSet.updateRow() when the table has a composite primary key. Cases where table's primary key has only one column or there is no primary key at all are not affected.
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.
All released versions at
sourceforge.net.
For more details see
Jaybird 2.1 JDBC driver Java Programmer's Manual.