The TORPEDO reference implementation source code was altered as follows:

Removed the explicit setting of inverse relations in JDOBid, taking advantageof Kodo JDO's automatic relationship management instead.

Altered the findHighBids test to take advantage of Kodo's support for JDOQL subqueries.

Kodo configuration settings were optimized for TORPEDO. In the JDO metadata, the JDOAuction.bids and JDOAuction.item fields were placed in the default fetch group. The JDOAuction.bids field was also configured to use a join for eager fetching (rather than a parallel select).

You may notice that the placeBid and place2Bids tests do not select any data. This is because TORPEDO calls the PersistenceManager.getObjectById method with the "validate" parameter set to false, allowing Kodo to return hollow objects (subject to a configuration property). Over the course of the tests, only the primary key state of these hollow objects is accessed; therefore, the hollow objects never require a trip to the database. Note that in a database with proper foreign keys, it is still impossible to violate the integrity of the data during these tests. An attempt to insert a JDOBid with a reference to a non-existent JDOAuction or JDOUser will fail, as it should.

SolarMetric
gcamp@solarmetric.com
www.solarmetric.com/

The number of database hits required to accomplish the operation is given. Following the link provides raw results, SQL and additional operation specific configuration information and analysis.