Core Data Predicate Bug?
Core Data Predicate Bug?
- Subject: Core Data Predicate Bug?
- From: ALEXander <email@hidden>
- Date: Sat, 16 May 2009 14:13:48 +0200
Hello,
I am currently developing a Core Data Application. I have an entity
(set) with a boolean attribute 'isActive' (optional, non-transient,
non-indexed, default NO). For some of my objects, this attribute is
set to YES. There is another entity (control) with a to-one
relationship to a set.
The problem occurs when saving and reopening a document: If I use a
predicate in a fetch request for the entity control which contains a
predicate format string like @"set.isActive == YES", no objects are
returned. Before saving and reopening, the correct objects are
returned. How can that happen? I know (by looking at the data with
the pre-built core data entity interfaces from IB) that there are
objects where that predicate is true.
To me, this is a bug. But of course, I hope to be wrong. One remedy is
to issue a [[self managedObjectContext] save] command before doing the
fetch, but this is very slow and therefore not suitable in my case.
Just issuing processPendingChanges does not work.
Pointers to a solution/workaround would be very much appreciated.
ALEXander.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden