Collections are cached seperatedly.
If you cache classes but not collections, the ids of the collectiosn will be collected from the DB every time.
And the reverse is true as well.

On 7/4/06, G. Richard Bellamy <[EMAIL PROTECTED]> wrote:

I need some help getting my head around something. What is the purpose of enabling the cache on relations?

 

If I've got a model with classes that are cacheable, but I don't cache the collections (relations), what is the consequence?

 

If I've got a model with a mixture of cacheable classes, but I DO cache the collections (relations), what happens?

 

It seems to me that if I enable caching on the classes, then I wouldn't need to cache the collections, since each item in the collection would then be cached.

 

- Richard


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users

Reply via email to