Re: Force Refresh Relation
Re: Force Refresh Relation
- Subject: Re: Force Refresh Relation
- From: Alan Ward <email@hidden>
- Date: Wed, 19 Sep 2007 22:24:04 -0600
"don't use the shared EC" is very much like "use
ec.invalidateAllObjecs()"
Both are not good advice.
Alan
On Sep 19, 2007, at 9:16 PM, Lachlan Deck wrote:
On 20/09/2007, at 12:40 PM, Kieran Kelleher wrote:
Yes, don't use the shared ec at all.
That's a sledge hammer approach... as it works well otherwise....
so I'm looking for info specifically on the aforementioned
situation. i.e., why it's occurring rather than just 'don't use...'.
Thanks.
On Sep 19, 2007, at 9:34 PM, Lachlan Deck wrote:
On 20/09/2007, at 12:01 AM, Alan Ward wrote:
On Sep 19, 2007, at 5:00 AM, Kieran Kelleher wrote:
I think that was referred to as the "sledge hammer" approach in
a WWDC session a few years ago ;-)
Indeed. You should never need to do that.
I wish that was true for the shared ec. I'm finding that unless I
invalidateAllObjects on the shared ec that it fails to release
old objects and fails to fetch new objects added to the database
by another app.
Any ideas on this?
with regards,
--
Lachlan Deck
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:
40apple.com
This email sent to email@hidden
_______________________________________________
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