• 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
re: refreshObject doesn't seem to work
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

re: refreshObject doesn't seem to work


  • Subject: re: refreshObject doesn't seem to work
  • From: Steve Steinitz <email@hidden>
  • Date: Thu, 9 Oct 2008 14:36:47 +1100

Hi Ben,

Thanks for your reply.  I was hoping to hear from you.

On 8/10/08, Ben Trumbull wrote:

Core Data for a multi-user

How is this configured ?  Through distributed notifications
replicating changes, or a network file system mount ?  If the later,
is it AFP ?

We're not yet using distributed notifications (and, they're not as distributed as their name implies :). We use a Thecus network drive over AFP.


I've 'enhanced' refreshObject

Refreshing either never merges (like rollback) or always merges (like byPropertyObjectTrump) depending on the flag parameter.

Ah, what I want is byPropertyStoreTrump. I wonder if I could get refreshObject to behave that way?


1.  re-fetch all the relevant managedObjects (arrayController fetch)
2.  call the above refreshObject on all of today's sales, every
bike-mold (a sort of bike template) and every bike

That should be enough on its own. In step 1, do you fetch the related objects as well?

Not systematically over the object graph partly because fetch only fetches new objects -- it doesn't update existing objects -- and partly because I questioned the saneness of the approach. I do traverse selected relationships, otherwise I just [arraycontroller fetch] relevant entities.


We only generate optimistic locking errors on save, so I'm not sure what this means.

Sorry, that's just my fuzzy thinking: I also save as part of the refresh process. Thanks for the useful clarification. (Its a separate subject but shouldn't calling refreshObject avoid the optimistic locking error on save?)


Ben, how would you approach solving this? Do you think refreshObject's byPropertyObjectTrump vs byPropertyStoreTrump behavior is relevant?

Thanks,

Steve

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: refreshObject doesn't seem to work
      • From: Ben Trumbull <email@hidden>
References: 
 >re: refreshObject doesn't seem to work (From: Ben Trumbull <email@hidden>)

  • Prev by Date: Re: Optimized pixel manipulation
  • Next by Date: Re: silly event question 'cuz i'm a n00b
  • Previous by thread: re: refreshObject doesn't seem to work
  • Next by thread: Re: refreshObject doesn't seem to work
  • Index(es):
    • Date
    • Thread