db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jdo-comm...@db.apache.org
Subject [Apache JDO Wiki] Updated: TechnologyCompatibilityKit
Date Sun, 27 Feb 2005 00:52:18 GMT
   Date: 2005-02-26T16:52:18
   Editor: CraigRussell
   Wiki: Apache JDO Wiki
   Page: TechnologyCompatibilityKit
   URL: http://wiki.apache.org/jdo/TechnologyCompatibilityKit

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -10,7 +10,7 @@
  *the mapping.
 A single schema, data set, object model and mapping will be used to test conformance for
as much of the specification as is possible.  For those areas that aren't covered by this
master variable set, the TCK will include variations on the master variable set for testing.
 
-It is a design goal of the TCK to reduce the number of permutations of these variables. 
In order to minimize the number of database schemata, the the TCK aims to generate, via a
DDL generator, any database schemas required.  It is not expected that the first version of
the JDO 2.0 TCK will include such a generator.  Until such time, database schemata will be
maintained manually.  In an effort to eliminate the number of vendor-specific database products,
SQL92 will be used to express the database schemata, and implementations will be able to test
their conformance against any number of database vendors' products.  We have not yet determined
to what degree variations from the TCK's schemata will affect conformance test results.
+It is a design goal of the TCK to reduce the number of permutations of these variables. 
In order to minimize the number of database schemata, the TCK aims to generate, via a DDL
generator, any database schemas required.  It is not expected that the first version of the
JDO 2.0 TCK will include such a generator.  Until such time, database schemata will be maintained
manually.  In an effort to eliminate the number of vendor-specific database products, SQL92
will be used to express the database schemata, and implementations will be able to test their
conformance against any number of database vendors' products.  We have not yet determined
to what degree variations from the TCK's schemata will affect conformance test results.
 
 = JDO TCK Assertions =
 
@@ -28,7 +28,7 @@
 '''Current Spreadsheet Version'''
 
 Download the current version of the assertions spreadsheet [attachment:JdoTckAssertionsTable.sxc
here]. 
-It is in Star``Office/Open``Office format. This version adds new assertions to the query
chapter covering JDOQL extensions in JDO 2.0. Furthermore it updates the assertions about
JDOPersmissions.
+It is in Star``Office/Open``Office format. This version adds new assertions to the query
chapter covering JDOQL extensions in JDO 2.0. Furthermore it updates the assertions about
JDOPermissions.
 
 = TCK ToDo =
 This is the list of tasks required to complete the JDO 2.0 TCK.
@@ -40,4 +40,3 @@
  ||DetachedObjects||Design and write tests for detached objects||Matthew Adams||?/05||
  ||--||Rewrite examples in Chapter 15 to use the Company model; associate each example with
a specific test case via assertion conditional text.||TBD||?/05||
  ||--||Write the rules vendors must follow in running the TCK to demonstrate compliance with
the specification||TBD||?/05||
-

Mime
View raw message