From: "email@hidden" <email@hidden>
To: Anjo Krank <email@hidden>
Cc: Shravan Kumar. M <email@hidden>; WO Dev Group <email@hidden>
Sent: Mon, February 8, 2010 6:14:14 PM
Subject: Re: refresh EC after call to ERXEOAccessUtilities.updateRowsDescribedByQualifier()?
Good point .. That trick presumed that the update you performed didn't impact a qualified key.
forgetObject wouldn't remove from to-many relationships, right? So be careful on that.
Long story short -- messing around behind eof's back is a pain.
Sent from my iPhone
On Feb 8, 2010, at 3:55 AM, "Anjo Krank"<
email@hidden> wrote:
> Wouldn't make much sense.
>
> - you're using these methods to NOT fetch the involved objects. If you're doing the fetch, you might as well save them by modifying the objects
> - if you fetch them *after* the modification, then, depending on your qualifier, you might not get anything back at all (say, modifying status=done where status=new)
>
> What you *can* do is filter the EC's registeredObjects() with the same qualifier, keep the GIDs, then update, then invalidate those
objects. As for the deleted objects, you should forgetObject() them.
>
> Cheers, Anjo
>
> Am 08.02.2010 um 06:04 schrieb Shravan Kumar. M:
>
>> 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 withfetchSpec.setRefreshesRefetchedObject(true) and with same qual used in updateRowsDescribedByQualifier()?
>>
>> From: Mike Schrag <
email@hidden>
>> To: Kieran Kelleher <
email@hidden>
>> Cc: Shravan Kumar. M <
email@hidden>; WO Dev Group <
email@hidden>
>> Sent: Sun, February 7, 2010 9:32:38 PM
>> Subject: Re: refresh EC after call to ERXEOAccessUtilities.updateRowsDescribedByQualifier()?
>>
>> 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 might do it.
>>
>> On Feb 7, 2010, at 10:59 AM, Kieran Kelleher wrote:
>>
>>> 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 ERXEOAccessUtilities.updateRowsDescribedByQualifier()/ ERXEOAccessUtilities.deleteRowsDescribedByQualifier() API's, such that only the effected EO's in the EC gets updated as per these actions?
>>>>
>>>> Thanks in advance,
>>>> Shravan Kumar. M
>>>> ---------------------------
>>>>
>>>> __________________________________________________
>>>> Do You Yahoo!?
>>>> Tired of spam? Yahoo! Mail has the best spam protection around
>>>> http://mail.yahoo.com/