Re: Best Strategy for Cacheing
Re: Best Strategy for Cacheing
- Subject: Re: Best Strategy for Cacheing
- From: Lachlan Deck <email@hidden>
- Date: Fri, 24 Oct 2008 08:42:27 +1100
Hi David,
On 23/10/2008, at 9:21 PM, David Avendasora wrote:
I've got a recursive structure in my model:
Part <->> Routing <->> RoutingStep <->> RoutingComponent <<-> Part
<...>
I think I've reached the point where having the data persisted in
the DB and actually part of the model and therefor managed by EOF is
going to be more efficient. I know I'll have data-freshness issues
with this strategy, but it will also make this data more easily
accessible from the outside of the WO system through things like
Crystal Reports.
I'm wondering what the best way to handle this will be. Am I going
down the wrong road in the first place?
I'd be looking at the shared ec for reading purposes, custom ecs (as
you're doing) for edits.
You can use ERXEOControlUtilities.clearSnapshotForRelationshipNamed to
clear cached relationships after for example inserting a record into a
toMany relationship in an ec. etc
with regards,
--
Lachlan Deck
_______________________________________________
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