Re: Caching reference data
Re: Caching reference data
- Subject: Re: Caching reference data
- From: Ben Ketteridge <email@hidden>
- Date: Sun, 17 Oct 2004 19:01:18 +0100
On Sun, 17 Oct 2004 09:57:56 -0700 (PDT), Jason McInnes
<email@hidden> wrote:
> I want the benefit of caching these reference types
> without the overhead of having to do the
> localInstanceOfObject step storing them in arrays on
> my Application object, and I'd like to not have to
> change my model (e.g., storing just the user name on
> reference types rather than a relationship to user).
> Am I out of luck?
Yes, basically.
If you want the power of WORelationships that change every time the
object changes, then, clearly, the object is not truly static.
Therefore, it does not belong in the EOSharedEditingContext. Such a
Context is for 'true' static data that never* changes.
*Well, almost always never... you can use localInstanceOfObject on the
rare occassion that the reference data changes, but the existing
shared instances may well not get the updates without being refreshed.
Hmmm, sounds to me like a case for a maintenance program to maintain
'reference data' outside the main program.
$0.02,
Ben Ketteridge
ps. caveat - I've not used EOSharedEditingContexts for a few years,
though maybe I ought to reconsider adding such optimisations to our
static data.
--
| Ben Ketteridge email@hidden, aka Gremlin |
| It is by caffeine alone that I set my mind in motion. |
| It is by the coffee that the thoughts acquire speed, |
| the lips acquire stains, the stains become a warning. |
| It is by caffeine alone that I set my mind in motion. |
_______________________________________________
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