As far as I understand:
1) Castor does cache only for db.load(), for OQL, it always hits the
database. And the cache is LRU with CountLimit or TimeLimit.
2) Castor can use external Transaction Manager, check
JDO.setTransactionManager().
Regards
------------
Zhongling "Alex" Li
-----Original Message-----
From: One Way [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 22, 2001 9:42 PM
To: [EMAIL PROTECTED]
Subject: [castor-dev] Castor overhead, cache, etc
I may be misunderstanding Castor, so here are some simple questions:
1) Suppose, Castor is used to retrieve, say, 500 rows from a table.
Suppose, data are retrieved for presentation purposes, transactions are
not needed. What overhead will Castor introduce comparing to the
regular JDBC approach?
2) Suppose that the data returned from the above query do not change
often (or at all). Can Castor cache 500 rows from previous query? If
yes, can Castor run OQL queries against cache instead of db?
3) Does Castor support EJB Container Managed transactions?
Thanks in advance
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
