Hi Chris,
Christopher Lowe wrote:
Hi All,
I have the following relationship. A Supplier has several
products (Rooms) and each product has several rates. Room is a Product hence
an inheritance relationship between them. The mappings are defined below.
I'm trying to perform a simple q
Hi All,
I have the following relationship. A Supplier has several
products (Rooms) and each product has several rates. Room is a Product hence
an inheritance relationship between them. The mappings are defined below.
I'm trying to perform a simple query to return the suppliers with pro
Hi Chris,
I checked in a fix for OJB-93. If possible please test latest version
from SVN OJB_1_0_RELEASE branch. This fix will be included in next
upcoming version (OJB 1.0.5).
regards,
Armin
Armin Waibel wrote:
Hi Chris,
Christopher Lowe wrote:
Hi All,
I ran the junit test suite for
Hi Bruno,
in OJB 1.0.2 we fixed a bug with partially materialized objects under
heavy load. Assume that this bug cause your problem.
http://db.apache.org/ojb/release-notes.txt
I would recommend the migration to OJB 1.0.4.
But take care of changes between 1.0.1 and 1.0.4 (e.g. complete
refacto
Hi Chris,
Christopher Lowe wrote:
Hi All,
I ran the junit test suite for the broker api and got the same
result. When a base class object is deleted the corresponding record in the
database is removed but not the super class object record. I ran only the
testDelete() method in the Inher
Hi All,
I ran the junit test suite for the broker api and got the same
result. When a base class object is deleted the corresponding record in the
database is removed but not the super class object record. I ran only the
testDelete() method in the InheritanceMultipleTableTest class. I'm at
Hello,
I now have spent a lot of time debugging 2 batch processing.
First processing creates a simple 1-n couple of object (consider that class
UnityCar refers a class Unity with 1-n relation) . Creation is done like
this :
- tx.begin()
- Unity u = new Unity()
- tx.lock(u, Transaction.WRITE);
-
