• 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: EOGenerator and takeStoredValueForKey dumb question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOGenerator and takeStoredValueForKey dumb question


  • Subject: Re: EOGenerator and takeStoredValueForKey dumb question
  • From: Anjo Krank <email@hidden>
  • Date: Tue, 22 Aug 2006 22:13:21 +0200


Am 22.08.2006 um 22:04 schrieb Chuck Hill:

It is not supposed to. validateAddress is intended to be called _before_ setAddress is called. Right, wrong, or weird, that is how EOF is intended to work. Objects are permitted to be invalid and validity is checked during saveChanges().

Which is totally reasonable given how WO works: where else would you keep invalid data for the user to fix?


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


References: 
 >EOGenerator and takeStoredValueForKey dumb question (From: Miguel Arroz <email@hidden>)
 >Re: EOGenerator and takeStoredValueForKey dumb question (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: Reusable translated button
  • Next by Date: Re: Using distinct in to-many relationship?
  • Previous by thread: Re: EOGenerator and takeStoredValueForKey dumb question
  • Next by thread: Why we should try!?
  • Index(es):
    • Date
    • Thread