On 10 Apr 2011, at 19:52, Carter R. Harrison wrote:
>
> On Apr 10, 2011, at 1:29 PM, Quincey Morris wrote:
>
>> On Apr 10, 2011, at 06:52, Carter R. Harrison wrote:
>>
>>> Can anybody ever think of a scenario where [NSManagedObject isInserted]
>>> equals NO for an object that is initially fetched from the context? And no
>>> the object has not been deleted from the context prior to calling
>>> isInserted.
>>
>> What do you mean by "initially fetched"? The object should return YES for
>> "isInserted" from the time it's inserted to the time the store is
>> committed/saved. It's not clear where in this timeline your "initially" is
>> pointing.
>>
>
> I'm creating and NSManagedObject with [NSManagedObject
> initWithEntity:insertIntoManagedObjectContext:] and for the context I'm
> passing nil. Later I call [NSManagedObjectContext insertObject:] and pass in
> the same NSManagedObject that was initialized earlier.
>
> On a subsequent run of my application I fetch the object from the store and
> call [NSManagedObject isInserted]. Without fail it always returns NO.
Think of it as being equivalent to:
- (BOOL)isInserted;
{
return [[[self managedObjectContext] insertedObjects] containsObject:self];
}
Thus, objects only return YES when inserted into a context and not yet
persisted._______________________________________________
Cocoa-dev mailing list ([email protected])
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
