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 Wed, 19 Jul 2006 17:43:56 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:

- == Snapshot Summary ==
+ == Snapshot Summary ==
  The Derby 10.2 release will expose many new features. Currently, we
  expect this release to appear in the autumn of 2006. Before then, we
- would like provide snapshots of our work-in-progress so that the
+ would like to provide snapshots of our work-in-progress so that the
  community can help find bugs. The following 10.2 features are ready
  for testing. In general, user documentation is not available yet.
@@ -38, +38 @@

  == JDBC4 Status ==
- JDBC4 support was compiled using Mustang build 86. Earlier builds of Mustang will not work
with the snapshot.
+ JDBC4 support was compiled and tested using Mustang build 91. However, you can probably
use any Mustang version from build 86 onwards.
  When run on the jdk1.6 platform, Derby 10.2 exposes the JDBC4 api. The
  following JDBC4 features have been coded and are ready for the
@@ -61, +61 @@

  || '''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.||
+ ||New streaming overloads||Mustang build 91 introduced new, lengthless overloads for the
streaming apis. Derby has not implemented these overloads yet. For the complete list of these
methods, see http://issues.apache.org/jira/browse/DERBY-1417. ||NOT compliant.||
- The snapshot will NOT comply with the following JDBC3 features
- which the JDBC4 spec clarifies are mandatory:
- || '''Feature'''|| '''Description''' || '''Compliance''' ||
- ||Implicit closing||The JDBC4 spec clarifies that insensitive, scrollable result sets should
not close implicitly when scrolled past the last row. Derby's embedded client violates this
contract.||NOT compliant.||
- ||Procedure invocation||The JDBC4 spec clarifies that stored procedures can be invoked by
Statement.executeQuery(). Derby does not support this usage yet.||NOT compliant.||
  == Scrollable, Updatable ResultSets (Insensitive) Status ==

View raw message