Title: JDO Object caching - db.load() versus OQLQuery.execute()

Hello!

First off, I want to express my thanks to the Castor open-source developers - I have been using Castor JDO and XML for a while, and it has worked out quite well for me.

I would appreciate any feedback on the following object caching issue.  I noticed that caching appears to work fine with the db.load() method, but does not work with OQLQuery.execute().  In the latter case, Castor appears to be making calls to the back-end for every query.  I currently use MySQL as the back-end DB, and confirmed this behavior using MySQL logging. Other developers had posted similar messages (see the thread "How to make cache works?") - has there been any resolution?

Many thanks!

Prabhu Balaraman
Manager, Business Systems Support
BOC Gases, NJ


_____________________________________________________________________
This e-mail has been scanned for viruses by the WorldCom Internet Managed Scanning Service - powered by MessageLabs. For further information visit http://www.worldcom.com

Reply via email to