db-ojb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Kalén <martin.ka...@curalia.se>
Subject Re: Postponing 1.0 until Weds, Jun 23
Date Mon, 21 Jun 2004 19:03:27 GMT
Martin Kalén wrote:

> With these issues out of the way, these are the results running
> ant junit
> against db-ojb HEAD from CVS as of June 21 2004 12:30 UTC
> with Sun JDK 1.4.2_04 on Windows XP SP 1, Oracle9i Personal rel
> (with OJB.skip.issues=true in build.properties):
> "
>     [junit] Running org.apache.ojb.broker.AllTests
>     [junit] Tests run: 402, Failures: 0, Errors: 3, Time elapsed: 
> 116,328 sec

1) BlobTest.testReadNullBlob
Incorrect field mappings for Torque: Oracle confused when getting
data from [BC]LOB with null-data.

Already resolved by Armins commit for issue OJB-268

2) BlobTest.testBlobInsertion
The test case uses long [BC]LOB values and I had P6Spy activated,
causing native Oracle LOB handling to fail (it must have direct
access to the OracleConnection, OraclePreparedStatement etc).

There have been reports on the list about using Oracle LOBs in a managed
environment (eg WebLogic) - these issues are probably related.

I will open up a separate issue and adding a patch with better info
in the exceptions thrown when native Oracle LOB handling can't be used.

However; the BlobTest.testBlobInsertion can be considered OK as it
passes with the properties that OJB ship with.

3) OptimisticLockingTest.testTimestampLock
See my mail re "Nanosecond precision makes optimistic locking unusable with Oracle"

>     [junit] Running org.apache.ojb.odmg.AllTests
>     [junit] Tests run: 196, Failures: 0, Errors: 1

Haven't looked yet - on it... ;-)


Martin Kalén
Curalia AB              Web:  http://www.curalia.se
Orrspelsvägen 2B        Mail: info@curalia.se
SE-182 79  Stocksund    Tel:  +46-8-410 064 40

To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org

View raw message