Re: NSPredicate with CoreData SQL store behavior
Re: NSPredicate with CoreData SQL store behavior
- Subject: Re: NSPredicate with CoreData SQL store behavior
- From: Jesse Grosjean <email@hidden>
- Date: Sat, 18 Mar 2006 23:20:21 -0500
mmalc,
I've created an example where this isn't the case [...]
That *looks* like a bug.
// change value in context
[entryData setValue:@"mytitle" forKey:@"title"];
Change this to:
[entryData setValue:@"mytitle" forKey:@"title"];
[entry setValue:@"newName" forKey:@"name"];
and the fetch succeeds...
Please file a bug report.
Thanks for your help on this. I've submitted a bug report and your
workaround seems to be working well. And wow, this makes Coredata
much more fun to use, I always wished the latest changes were
reflected in the search results and now they are! Now I get to go
make my app run faster and rip out code that's no longer needed :)
Jesse
_______________________________________________
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