• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
EOEditingContext help
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • Follow-Ups:
    • Re: EOEditingContext help
      • From: David Avendasora <email@hidden>
  • Prev by Date: Subject: Re: Cocoa WebObjects Integration
  • Next by Date: Re: Migrations and Default Values
  • Previous by thread: Subject: Re: Cocoa WebObjects Integration
  • Next by thread: Re: EOEditingContext help
  • Index(es):
    • Date
    • Thread