Re: CoreData validation strangeness
Re: CoreData validation strangeness
- Subject: Re: CoreData validation strangeness
- From: Shaun Wexler <email@hidden>
- Date: Sat, 11 Mar 2006 13:23:27 -0800
On Mar 11, 2006, at 12:57 PM, mmalcolm crawford wrote:
It's not clear why this is specific to Core Data.
Well this is my _first_ attempt at using CoreData, vs my custom SQL
client lib. ;)
Have you checked to see if the validation method is being called
when you expect it to be...
Yes. In the cases I indicated, the validation method is NOT called
in the two different backspace scenarios...
I assume that the following methods are implemented in a subclass
of NSManagedObject?
No, these methods are implemented in my AppDelegate subclass. The
entity returns plain-vanilla instances of NSManagedObject.
It is much more efficient to create a predicate template and
substitute values than to re-parse the format string each time.
Thanks for verifying that; I parsed the doc's earlier today, and
thought I might be doing it inefficiently (especially upon every
keypress). Q: is there a better way to perform this check, as the
user types? Or should it only be done upon enter and/or end
editing? Same question, regarding a large compound predicate and
search field over many entities?
It's not clear why these methods don't follow the prescribed form
for managed object accessors?
Because they're not. ;)
Everything works fine, until I return NO from the validation method,
and then backspace is the next keypress. It also fails [to call the
validation method] if you enter a key, backspace, then enter that
same key again.
--
Shaun Wexler
MacFOH
http://www.macfoh.com
'I was thinking of the immortal words of Socrates, who said,
"I drank what?!!"' - Val Kilmer, Real Genius, 1985
_______________________________________________
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