db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "TenTwoSnapshot" by RichardHillegas
Date Fri, 09 Jun 2006 23:21:00 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by RichardHillegas:

  || '''Feature'''|| '''Description''' || '''Compliance''' ||
  ||Large objects||JDBC4 adds new methods for creating, inserting, and releasing Blobs and
Clobs. These methods appear on the following old JDBC objects: Connection, !PreparedStatement,
Blob, and Clob. The snapshot will implement the new methods on Connection and !PreparedStatement.
The JDBC4 spec also requires that the old, JDBC3 Blob and Clob interfaces be fully implemented
and that Blob/Clob be updateable through JDBC3 !ResultSets method. The snapshot will NOT fully
implement the Blob/Clob methods, nor will it let you update large objects through !ResultSets.||NOT
  ||Late-breaking changes||The JDBC4 spec continues to evolve briskly. Every week the JDBC4
expert group approves changes to the signatures, return values, and semantics of JDBC objects
and methods. It takes a while for spec changes to percolate into Mustang builds. When a spec
change appears in Mustang, the Derby team first supplies a vacuous implementation so that
Derby will compile cleanly. Some time after that, the Derby team supplies a real, compliant
implementation. It is virtually certain that the snapshot will contain some vacuous implementations
of late-breaking changes. It is also virtually certain that the snapshot will grow stale measured
against new, weekly Mustang builds. As the snapshot ages, we should expect that Derby clients
will raise occasional abstract method exceptions.||NOT compliant.||
+ ||New streaming overloads||Mustang build 86 introduced new overloads for the large object
and streaming apis, which use a "long" length parameter. Derby does not yet implement these.
These methods include overloads of the setXXXStream() methods on !PreparedStatement/!CallableStatement;
updateXXXStream() methods on !ResultSet; and the !ResultSet update() methods for Blob, Clob,
NClob, and N!CharacterStream.||NOT compliant.||
  The snapshot will NOT comply with the following JDBC3 features
  which the JDBC4 spec clarifies are mandatory:

View raw message