Question

I have a webservice that will send data down to the phone. Sometimes it will already exist as a core data object and sometimes it will be new. I have a unique reference for the item so I basically want to search to see if the object exists and if not then it saves it to the core data storage. If it exists then in an ideal world I want to update the object.

At the moment I remove all objects and fill them again from my webservice, but obviously this isn’t practical when there are lots of items.

Answer 1

You should have something like an unique ID in you Entity. Then you fetch entity with that ID from Core Data if it’s empty you create a new one, otherwise you use fetched one. So what’s the problem with that? If you use concurrency that may be harder.