• 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: Formatting Core Data Conflict List
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

re: Formatting Core Data Conflict List


  • Subject: re: Formatting Core Data Conflict List
  • From: Ben Trumbull <email@hidden>
  • Date: Thu, 29 Jan 2009 23:01:02 -0800

Hi Steve,

It's just an array of dictionaries with a fixed set of keys.

The newVersion and oldVersion shows the version count on the objects really has changed. A few things to note. First, you've set a merge policy on the NSManagedObjectContext right ?

Some sources of conflicts that surprise people are (a) dirtying transients, (b) maintaining last mod timestamps (c) making blind changes in -willSave or validation callbacks, or (d) updating the contents of a to-many relationship.

- Ben

_______________________________________________

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:
    • Analyzing Core Data Conflict List [was: Formatting Core Data Conflict List]
      • From: Steve Steinitz <email@hidden>
  • Prev by Date: NSAttributesString -size is often very innaccurate
  • Next by Date: Re: NSAttributesString -size is often very innaccurate
  • Previous by thread: Formatting Core Data Conflict List
  • Next by thread: Analyzing Core Data Conflict List [was: Formatting Core Data Conflict List]
  • Index(es):
    • Date
    • Thread