• 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: Forcing Core Data to save attribute changed behind its back?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Forcing Core Data to save attribute changed behind its back?


  • Subject: Re: Forcing Core Data to save attribute changed behind its back?
  • From: Sixten Otto <email@hidden>
  • Date: Tue, 24 Jul 2012 05:31:22 -0700

On Mon, Jul 23, 2012 at 3:03 PM, Sean McBride <email@hidden> wrote:
> when I change it, instead of the usual setAttribute:newValue I mutate the object directly.
>  - will/didChangeValueForKeyPath: but that's not a sufficient 'kick'

Out of random curiousity, does this big mutable object you're updating
change in a way Core Data would see? Does the object's "before" state
-isEqual: its "after" state?
_______________________________________________

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: Forcing Core Data to save attribute changed behind its back?
      • From: Sean McBride <email@hidden>
References: 
 >Forcing Core Data to save attribute changed behind its back? (From: Sean McBride <email@hidden>)

  • Prev by Date: Re: Profound UITableView rendering-performance problem, but only at certain positions?
  • Next by Date: Re: Forcing Core Data to save attribute changed behind its back?
  • Previous by thread: Forcing Core Data to save attribute changed behind its back?
  • Next by thread: Re: Forcing Core Data to save attribute changed behind its back?
  • Index(es):
    • Date
    • Thread