Mailing-List: contact derby-commits-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: derby-commits@db.apache.org
Date: Thu, 25 May 2006 20:03:09 -0000
Message-ID: <20060525200309.29295.55377@ajax.apache.org>
Subject: [Db-derby Wiki] Update of "TenTwoSnapshot" by RichardHillegas

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

New page:
'''Table of Contents'''
[[TableOfContents(3)]]


== 10.2.0.1 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
community can help find bugs. The following 10.2 features are ready
for testing. In general, user documentation is not available yet.

|| '''New Feature'''|| '''Link to JIRA entries''' || '''Code Status''' || '''Documentation''' ||
|| Scrollable Updatable !ResultSets|| See below. || Complete || - ||
|| JDBC4|| See below. || See below. || - ||
|| Unary plus/minus for parameters || [http://issues.apache.org/jira/browse/DERBY-582 DERBY-582] || Complete || - ||
|| FOR UPDATE clause || [http://issues.apache.org/jira/browse/DERBY-231 DERBY-231] || Complete || - ||
|| Client timeout mechanism || [http://issues.apache.org/jira/browse/DERBY-506 DERBY-506] || Complete || - ||
|| Optimizer directives || [http://issues.apache.org/jira/browse/DERBY-573 DERBY-573] || Complete || - ||
|| Xml support for XPath and JDBC || [http://issues.apache.org/jira/browse/DERBY-688 DERBY-688] || - || - ||
|| Grant Revoke || [http://issues.apache.org/jira/browse/DERBY-464 DERBY-464]  || - || - ||
|| Online backup || [http://issues.apache.org/jira/browse/DERBY-239 DERBY-239] || Complete || - ||
|| DRDA USRSSBPWD Security Mechanism || [http://issues.apache.org/jira/browse/DERBY-528 DERBY-528] || - || - ||
|| Identity value restart || [http://issues.apache.org/jira/browse/DERBY-783 DERBY-783] ||  Complete || - ||
|| Internationalizing Client Messages || See below. || - || - ||
|| New builtin functions || [http://issues.apache.org/jira/browse/DERBY-475 DERBY-475] || Complete || - ||
|| New JDBC escape functions || [http://issues.apache.org/jira/browse/DERBY-592 DERBY-592] || Complete || - ||
|| Restrict client connections,derby.drda.securityMechanism  || [http://issues.apache.org/jira/browse/DERBY-928 DERBY-928] || Complete || - ||

For more information on the contents of the 10.2 release, see
[http://wiki.apache.org/db-derby/DerbyDevActivities].

== JDBC4 Status ==

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
community to test:

|| '''Feature'''|| '''Description''' || '''Compliance''' ||
||Driver autoloading||This lets applications open Connections to Derby databases without having to know the names of the Derby JDBC drivers.||Fully implemented.||
||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.||
||Statement events||This lets applications listen for events which invalidate or close Statements. The June snapshot will fire these events.||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 June snapshot will do this.	ever, the June snapshot  will omit 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 June snapshot will implement 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.||
||XML||JDBC4 introduces this optional datatype. Derby does not support the corresponding SQL XML datatype. Therefore the corresponding JDBC4 methods will throw SQLFeatureNotSupportedException.||Mandatory methods implemented.||
||SQLInput/SQLOutput||JDBC4 introduces these optional interfaces. Derby does not support the corresponding SQL structured and distinct datatypes. Therefore the corresponding JDBC4 methods will throw SQLFeatureNotSupportedException.||Mandatory methods implemented.||

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.||
||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.||

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.||

== SUR Status ==

Hey, Dag, could you fill this in?

== Grant/Revoke Status ==

Hey, Satheesh, could you fill this in?

== Internationalization Status ==

Hey, David, could you fill this in?