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 Sat, 26 Aug 2006 00:09:22 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:
http://wiki.apache.org/db-derby/TenTwoSnapshot

------------------------------------------------------------------------------
  ||Ease-of-development||This uses Annotations to simplify and parameterize the creation of
tabular !DataSets. Derby does not implement its own !QueryObjectGenerator. Instead, as the
spec allows, Derby forwards ease-of-development calls to Mustang's default !QueryObjectFactory.||Mandatory
methods implemented.||
  ||Wrapper pattern||This lets applications exploit vendor-specific behavior wrapped inside
JDBC objects.||Fully implemented, though Derby does not expose any vendor specific behaviour.||
  ||Statement events||This lets applications listen for events which invalidate or close Statements.||Fully
implemented.||
- ||SQLException subclasses||JDBC4 refines SQLException into new subclasses, each bound to
some range of error conditions. JDBC4 requires that implementations raise these refined exceptions
when the corresponding conditions occur. The snapshot does this.	However, the snapshot omits
the late-breaking SQLRecoverableException, whose vendor-specific semantics are not clear.
Although Derby does not raise this exception, we believe that Derby complies with the spec.||Mandatory
methods implemented.||
+ ||SQLException subclasses||JDBC4 refines SQLException into new subclasses, each bound to
some range of error conditions. JDBC4 requires that implementations raise these refined exceptions
when the corresponding conditions occur. 10.2 does this.	However, 10.2 omits the late-breaking
SQLRecoverableException, whose vendor-specific semantics are not clear. Although Derby does
not raise this exception, we believe that Derby complies with the spec.||Mandatory methods
implemented.||
  ||Miscellaneous methods||JDBC4 adds new methods and changes old methods on the following
JDBC objects: Connection, !CallableStatement, !DatabaseMetaData, !PreparedStatement, !ResultSet,
Statement, !DataSource, and !PooledConnection. The snapshot implements all of these methods
that are mandatory. Some optional methods will throw SQLFeatureNotSupportedException.||Mandatory
methods implemented.||
  ||!RowId||JDBC4 introduces this optional datatype. Derby does not support the corresponding
SQL ROWID datatype. Therefore the corresponding JDBC4 methods will throw SQLFeatureNotSupportedException.||Mandatory
methods implemented.||
  ||National string types||JDBC4 introduces these optional datatypes: NCHAR, NVARCHAR, LONGNVARCHAR,
NCLOB. Derby does not support the corresponding SQL datatypes. Therefore the corresponding
JDBC4 methods will throw SQLFeatureNotSupportedException.||Mandatory methods implemented.||
@@ -58, +58 @@

  The snapshot will NOT comply with the following features added by JDBC4:
  
  || '''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
compliant.||
+ ||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. 10.2 will NOT fully implement
the Blob/Clob methods, nor will it let you update large objects through !ResultSets.||NOT
compliant.||
  
  
  

Mime
View raw message