EOEditingContext help
EOEditingContext help
- Subject: EOEditingContext help
- From: Theodore Petrosky <email@hidden>
- Date: Sat, 18 Sep 2010 20:38:32 -0700 (PDT)
I have to update a whole bunch of objects. Method 1 says make a list of the objects, make the changes and saveChanges(). Seems really inefficient. If there were only 50 objects I would probably do that. So I created a procedure on backend. Basically, an update of all records that match a job number.
Of course this is making a change behind the back of my WO App. and someone may be looking at this data.
So what are my choices? go back to method 1. Looping through 500 records, then saving changes? Or is there a way to selectively invalidate these objects to force any other users to get fresh data?
Ted
_______________________________________________
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