You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by Thomas Dudziak <to...@first.gmd.de> on 2004/01/02 19:42:59 UTC
Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Hi,
today I tested some things with Hsqldb (instead of my usual MySql), and
found some problems with the version that is part of OJB:
The syntax
CREATE TABLE SOMETABLE ( ID integer IDENTITY, ATTR VARCHAR(32), PRIMARY
KEY(ID))
does not work (btw. this is the form that Torque and therefore the XDoclet
OJB module generates) because the old Hsqldb version assumes that two
primary keys are being generated via IDENTITY and PRIMARY KEY (though it
is the same field). This is an old bug that I submitted some months ago
to the Hsqldb team, and that is fixed in the new Hsqldb version.
The second thing is that it is not possible to use long/Long fields (that
map to BIGINT) as primarykeys with the old Hsqldb version. See the
changelog at
http://cvs.sourceforge.net/viewcvs.py/hsqldb/hsqldb-dev/doc/changelog_1_7_2.txt
for details.
So basically I hereby vote for updating to the 1.7.2RC1 version of Hsqldb
which is a release officially advertised on the Hsqldb site, prior to
releasing the OJB 1.0 final. This hopefully amounts to only rerunning the
tests; I'll try that today and post any results later on.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Thomas Dudziak dijo:
> On Sat, 3 Jan 2004, Antonio Gallardo wrote:
>
>> Hi:
>>
>> The HSQLDB 1.7.2RC1 is not a final version.
>> I think it is not a good idea to include a devel version in OJB 1.0
>
> Normally I'd agree with you, but if you look at the dev cycle of Hsqldb,
> then you'll notice that this is the first stable version of Hsqldb in over
> a year (after 20 or more intermediate versions) - the version with OJB is
> 1.7.1 dated 21. Oct 2002. So this is as stable as you can get in the near
> future. Also it fixes some - I think - serious bugs which is why I'd
> rather use this new version.
Hi:
Sorry for the noise and thanks for the info. After reading your answer, I
agree with you. :-D
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Posted by Antonio Gallardo <ag...@agsoftware.dnsalias.com>.
Hi:
The HSQLDB 1.7.2RC1 is not a final version.
I think it is not a good idea to include a devel version in OJB 1.0
Best Regards,
Antonio Gallardo.
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Posted by Jakob Braeuchi <jb...@gmx.ch>.
Thomas Dudziak wrote:
> 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.
i agree
> 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).
+ 1
jakob
>
> 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Posted by Thomas Dudziak <to...@first.gmd.de>.
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
Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Posted by Jakob Braeuchi <jb...@gmx.ch>.
hi tom,
in this case we'd better stay with the current versions of hsqldb and
torque. ojb 1.0 should be available *tomorrow*, so there's only little
time to hunt bugs.
just my 0.02 CHF
jakob
Thomas Dudziak wrote:
> On Sat, 3 Jan 2004, Jakob Braeuchi wrote:
>
>
>>hi tom,
>>
>>i tried simply replacing the hsqldb.jar with the new 1.7.2RC1. but then
>>the testcases no longer work !
>>even prepare-testdb created a database that i could not use. there are
>>two files OJB.properties and OJB.log but i miss OJB.script.
>>
>>is there anything else that needs to be changed as well to use 1.7.2 ?
>
>
> I had the same problem with the OJB tests though I have sucessfully used
> the 1.7.2rc1 in an OJB project of mine (with XDoclet module and torque).
> I have pinned the problem to the preparation of the test database, more
> specifically the call to the project-datasql-classpath target in the
> torque build file. It seems as if this step does not close the database
> correctly as there is still a lock file after the ant call:
>
> BUILD FAILED
> file:E:/projects/ojb/DB-OJB~1/build-torque.xml:181: java.sql.SQLException: The
> database is already in use by another
> process: org.hsqldb.LockFile@2df8dff[file =
> E:\projects\ojb\DB-OJB~1\target\test\OJB.lck, exists=true, locked=false,
> valid=false, ]: java.lang.Exception: checkHeartbeat(): lock file
> [E:\projects\ojb\DB-OJB~1\target\test\OJB.lck] is presumably locked by
> another process.
>
> In my personal project, I don't use the project-datasql-classpath target.
> I fear that there is a problem with the Torque version we use
> (3.0.2). I'll try 3.1 today to see whether that works better.
>
> Tom
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Posted by Thomas Dudziak <to...@first.gmd.de>.
On Sat, 3 Jan 2004, Jakob Braeuchi wrote:
> hi tom,
>
> i tried simply replacing the hsqldb.jar with the new 1.7.2RC1. but then
> the testcases no longer work !
> even prepare-testdb created a database that i could not use. there are
> two files OJB.properties and OJB.log but i miss OJB.script.
>
> is there anything else that needs to be changed as well to use 1.7.2 ?
I had the same problem with the OJB tests though I have sucessfully used
the 1.7.2rc1 in an OJB project of mine (with XDoclet module and torque).
I have pinned the problem to the preparation of the test database, more
specifically the call to the project-datasql-classpath target in the
torque build file. It seems as if this step does not close the database
correctly as there is still a lock file after the ant call:
BUILD FAILED
file:E:/projects/ojb/DB-OJB~1/build-torque.xml:181: java.sql.SQLException: The
database is already in use by another
process: org.hsqldb.LockFile@2df8dff[file =
E:\projects\ojb\DB-OJB~1\target\test\OJB.lck, exists=true, locked=false,
valid=false, ]: java.lang.Exception: checkHeartbeat(): lock file
[E:\projects\ojb\DB-OJB~1\target\test\OJB.lck] is presumably locked by
another process.
In my personal project, I don't use the project-datasql-classpath target.
I fear that there is a problem with the Torque version we use
(3.0.2). I'll try 3.1 today to see whether that works better.
Tom
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org
Re: Update to HSQLDB 1.7.2 RC1 for 1.0 final ?
Posted by Jakob Braeuchi <jb...@gmx.ch>.
hi tom,
i tried simply replacing the hsqldb.jar with the new 1.7.2RC1. but then
the testcases no longer work !
even prepare-testdb created a database that i could not use. there are
two files OJB.properties and OJB.log but i miss OJB.script.
is there anything else that needs to be changed as well to use 1.7.2 ?
jakob
Thomas Dudziak wrote:
> Hi,
>
> today I tested some things with Hsqldb (instead of my usual MySql), and
> found some problems with the version that is part of OJB:
>
> The syntax
>
> CREATE TABLE SOMETABLE ( ID integer IDENTITY, ATTR VARCHAR(32), PRIMARY
> KEY(ID))
>
> does not work (btw. this is the form that Torque and therefore the XDoclet
> OJB module generates) because the old Hsqldb version assumes that two
> primary keys are being generated via IDENTITY and PRIMARY KEY (though it
> is the same field). This is an old bug that I submitted some months ago
> to the Hsqldb team, and that is fixed in the new Hsqldb version.
>
> The second thing is that it is not possible to use long/Long fields (that
> map to BIGINT) as primarykeys with the old Hsqldb version. See the
> changelog at
> http://cvs.sourceforge.net/viewcvs.py/hsqldb/hsqldb-dev/doc/changelog_1_7_2.txt
> for details.
>
> So basically I hereby vote for updating to the 1.7.2RC1 version of Hsqldb
> which is a release officially advertised on the Hsqldb site, prior to
> releasing the OJB 1.0 final. This hopefully amounts to only rerunning the
> tests; I'll try that today and post any results later on.
>
> Tom
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org