Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 1977 invoked from network); 3 Jan 2004 13:10:34 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 3 Jan 2004 13:10:34 -0000 Received: (qmail 24551 invoked by uid 500); 3 Jan 2004 13:10:31 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 24529 invoked by uid 500); 3 Jan 2004 13:10:31 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 24516 invoked from network); 3 Jan 2004 13:10:30 -0000 Received: from unknown (HELO prosun.first.fraunhofer.de) (194.95.168.2) by daedalus.apache.org with SMTP; 3 Jan 2004 13:10:30 -0000 Received: from pille.first.gmd.de (pille [194.95.168.10]) by prosun.first.fraunhofer.de (8.12.10/8.12.10) with SMTP id i03DAULA003013 for ; Sat, 3 Jan 2004 14:10:30 +0100 (MET) Received: from localhost by pille.first.gmd.de (SMI-8.6/SMI-SVR4) id OAA29732; Sat, 3 Jan 2004 14:10:30 +0100 Date: Sat, 3 Jan 2004 14:10:29 +0100 (MET) From: Thomas Dudziak X-Sender: tomdz@pille To: OJB Developers List Subject: Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ? In-Reply-To: <3FF69AE2.8040806@gmx.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I did a quick test with torque 3.1 and hsqldb 1.7.2rc1, and it seems that using torque 3.1 would (at least) require some changes to the data xml file used by the tests (not much surprising), and to the dtd-entries in the schemas (database_3_0_1 -> database_3_1). Since this will also involve testing the unit tests with all databases that we (officially ?) support, this is probably not something for the 1.0 final release. Since I think that the update to hsqldb 1.7.2 and Torque 3.1 is important, could we then agree to the following ? : * Add paragraphs to the known issues section of the 1.0 final for both hsqldb and torque (see below), and use the old versions for the 1.0 final. * In the dev and for the 1.0.1 we update to Hsqldb 1.7.2 and Torque 3.1. We can also ask the Hsqldb folks when a final 1.7.2 can be expected. * Add a unit test that uses a BIGINT column as primarykey. * Change the test data handling to make it less dependent of the Torque version used (this is easier since Torque 3.1). As for the known issues I would put in something like: * OJB 1.0 uses Hsqldb 1.7.1. It might run with newer versions, but the unit tests of OJB won't work with Hsqldb 1.7.2RC1 (other versions newer than 1.7.1 not tested). * OJB 1.0 uses Torque version 3.0.2 for the unit tests. Newer versions won't work, though they are likely to work with the schemas generated by the XDoclet OJB module (use the dtdUrl attribute of the torque schema subtask for specifying the new DTD Url). Tom --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org