Thanks for your suggestion Mike. Sorry, I did not get your statement: do you
mean after call to ERXEOAccessUtilities.updateRowsDescribedByQualifier(),
should I immediately call EOFetchSpec with
fetchSpec.setRefreshesRefetchedObject(true) and with same qual used in
updateRowsDescribedByQualifier
Thanks for your suggestion Kieran. At the moment I am just invoking
ec.refreshAllObjects(); Will update the code as advised and try out!
From: Kieran Kelleher
To: Shravan Kumar. M
Cc: WO Dev Group
Sent: Sun, February 7, 2010 9:29:06 PM
Subject: Re: refresh EC
Another option if your logic allows it, you could also just create a new EC at
this point, setting FetchTimestamp to System.currentTimeMillis() and then fault
in your object(s) that you are currently working with using
ec.faultForGlobalID(...)
On Feb 7, 2010, at 11:02 AM, Mike Schrag wrote:
>
for the update case, i was thinking just use the same qualifier with a
refreshesRefetchedObjects on a fetch spec i think that won't refresh
deleted objects, though, so I'm not sure the best way to do the delete case. if
the objects were fetched into the eo already, then refreshAllObjects mi
Off the top of my head, I would think something like this:
ec.setFetchTimestamp( System.currentTimeMillis() );
ec.refreshAllObjects();
On Feb 7, 2010, at 1:06 AM, Shravan Kumar. M wrote:
> Hello Group,
>
> Is there any efficient way to refresh EOEditingContext after call to
> ERXEOAccessUti
