Hello,

I have released new version of Jaybird. Following fixes were added:

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 are advised to upgrade to a new
version. Not doing so will cause data corruption when doing updates via
ResultSet.updateRow() when table has 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: 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".

Also the behavior with previous versions of FB will cause exception
while connecting to Firebird. The more intelligent solution will be
implemented in Jaybird 2.2.

Best regards,
Roman Rokytskyy