Re: SetDefaultFetchTimestampLag
Re: SetDefaultFetchTimestampLag
- Subject: Re: SetDefaultFetchTimestampLag
- From: David Griffith <email@hidden>
- Date: Mon, 07 Mar 2005 11:36:14 +0100
Thanks Chuck, I figured it was something like that...
Dave.
> At 11:08 PM 06/03/2005 +0100, David Griffith wrote:
>> Hi all,
>>
>> I have called in my session :
>>
>> this.defaultEditingContext().setDefaultFetchTimestampLag(300000);
>>
>> Should this cause data to be refreshed from the DB if more than 5 mins has
>> passed?
>>
> No, but that is a common misconception. See the EOEditingContext docs for
> setFetchTimestamp(long timestamp):
>
> Sets the receiver's fetch timestamp. When an editing context fetches
> objects from its parent object store, the parent object store can use the
> timestamp to determine whether to use cached data or to refetch the most
> current values. An editing context prefers that fetched values are at least
> as recent as its fetch timestamp. Note that the parent object store is free
> to ignore the timestamp; so this value should be considered a hint or
> request and not a guarantee.
>
> Note: Changing the fetch timestamp has no effect on existing objects in
> the editing context; it can affect only subsequent fetches. To refresh
> existing objects, invoke refaultAllObjects before you invoke
> setFetchTimestamp:.
>
>
> See also page 94-97 of Practical WebObjects and the topics on getting fresh
> data / refreshing data on www.wodev.com
>
>
> Chuck
>
>
>
> --
>
> Chuck Hill email@hidden
> Global Village Consulting Inc. http://www.global-village.net
>
_______________________________________________
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