• 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
does core data always call through the setPrimative methods?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

does core data always call through the setPrimative methods?


  • Subject: does core data always call through the setPrimative methods?
  • From: Roland King <email@hidden>
  • Date: Sun, 24 Jul 2011 16:46:01 +0800

Simple question but I'm not finding an answer in the docs or by googling.

I have a property Foo in my managed object and I want to add code in a subclass to update some internal state when Foo's changed. Is it sufficient override the setPrimitiveFoo: method, add my update code and call the superclass' version, i.e. does core data implement setFoo: by *always* calling the primitive method, setPrimativeFoo: or do I need to add the code in both setFoo: and setPrimitiveFoo:?


_______________________________________________

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: does core data always call through the setPrimative methods?
      • From: Jerry Krinock <email@hidden>
  • Prev by Date: Re: Core Data: I/O Error No Such Column
  • Next by Date: Re: NSDocument: Read-only types and autosavesInPlace
  • Previous by thread: Re: drawRect not getting called when needed under OS X
  • Next by thread: Re: does core data always call through the setPrimative methods?
  • Index(es):
    • Date
    • Thread