• 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
Uniquing data in Core Data
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Uniquing data in Core Data

  • Subject: Uniquing data in Core Data
  • From: Rick Mann <email@hidden>
  • Date: Wed, 14 Aug 2013 17:28:24 -0700
I have a boolean property on an Entity for which only one should ever be true. Is it really bad to implement a custom setter that loads every other instance in the MOC that's true and sets them all to false? My code is actually good about always clearing the current one before setting the new one, but when I'm debugging, I will copy data over from another device, and it can't clear the old one in this case.

--
Rick




_______________________________________________

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: Uniquing data in Core Data
      • From: Keary Suska <email@hidden>
  • Prev by Date: Cocoaheads tonight, Wednesday 9/14, at 7pm
  • Next by Date: Re: Uniquing data in Core Data
  • Previous by thread: Cocoaheads tonight, Wednesday 9/14, at 7pm
  • Next by thread: Re: Uniquing data in Core Data
  • Index(es):
    • Date
    • Thread