Re: Large to-many relationships and caching "Best Practise"
Re: Large to-many relationships and caching "Best Practise"
- Subject: Re: Large to-many relationships and caching "Best Practise"
- From: Mike Schrag <email@hidden>
- Date: Wed, 12 Aug 2009 10:25:05 -0400
This is pretty much exactly what I do as well. Just didn't know if
there was a "better way" of doing this and managing the cache.
Depending on how you're using these things:
http://webobjects.mdimension.com/wonder/api/er/extensions/eof/ERXEnterpriseObjectCache.html#ERXEnterpriseObjectCache(java.lang.String, java.lang.String, com.webobjects.eocontrol.EOQualifier, long, boolean, boolean, boolean)
This automatically stays up-to-date as the object graph changes. I've
only used this for app-global caches, but you should be able to use it
per-instance if you really wanted to. Certainly if you're going to try
to keep your custom cache up-to-date, you might as well use it.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden