Thanks Willeke, Jerry Krinock for your great hints and suggestions.
Indeed I use cocoa-bindings to Core-Data model in my UI, via
NSTableViewsColumns bound to a NSArrayController configured to work against the
"Species" entity. That is why Core-Data's inherent KVO/KVC validation seemed
the perfe
Some ideas, I don't know if it works:
in your validation method, change
NSArray *allSpecies = [self.managedObjectContext
executeFetchRequest:allSpeciesIDsFetchRequest error:nil];
NSArray *allCatalogIDs = [allSpecies valueForKeyPath:@"catalogID"];
if ([allCatalogIDs containsObject:*ioValu
Hello, Motti. I read your post. All 600+ words :)
> On 2014 Aug 30, at 03:58, Motti Shneor wrote:
> I would gladly settle on a UI-only validation (meaning, something that would
> validate a text field upon end-edit-session=
I would pursue that.
> but I don't know how to hook this on a bound
-dev-requ...@lists.apple.com wrote:
> Date: Sat, 30 Aug 2014 13:58:34 +0300
> From: Motti Shneor
> To: cocoa-dev@lists.apple.com
> Subject: How to Validate CoreData attribute value for uniqueness
> Message-ID: <270bab85-1588-4d1e-bf18-35aab9556...@bezeqint.net>
> Content-T
Hello everyone. Many discussions address this in many development forums. I
read them all, and was frustrated NOTHING of the suggested solutions actually
worked. Apple's documentation adds insult to injury, completely ignoring such a
common need for any real-world Core-Data modeled application.
