• 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: Read-Only Core Data Attributes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Read-Only Core Data Attributes


  • Subject: Re: Read-Only Core Data Attributes
  • From: Kay Roepke <email@hidden>
  • Date: Thu, 4 May 2006 17:27:39 +0200

Arggh. Sorry about that...I should train my infinite amount of monkeys better...

On 4. May 2006, at 10:04 Uhr, Jonathon Mah wrote:

My ideas:
1. Implement validation methods that return NO (unless the new value is equal to the current one).
2. Throw an exception in setter methods if the revision is read-only.
3. "Accept" setter messages, but simply ignore them (keep the attributes unchanged).


Which is the best way to enforce read-only attributes? I'm leaning toward using both 1 and 2 above.

How about:

4. Make the UI elements uneditable to prevent changing the entry.

If you're concerned about programmatic changes I'd go with 1. and/or 2., also.

-k
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Read-Only Core Data Attributes (From: Jonathon Mah <email@hidden>)

  • Prev by Date: Re: Problem with prebinding and Frameworks
  • Next by Date: Re: Cocoa & Java on Intel fails with "Java for ppc cannot run in this configuration"
  • Previous by thread: Re: Read-Only Core Data Attributes
  • Next by thread: [Newbie] Webkit Tutorial or how to load HTML-Source filled NSData into WebKit
  • Index(es):
    • Date
    • Thread