Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: CoreData - NSManagedObjectContext notifications - Save vs DidChange ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData - NSManagedObjectContext notifications - Save vs DidChange ?

Subject: Re: CoreData - NSManagedObjectContext notifications - Save vs DidChange ?
From: Jim Correia <email@hidden>
Date: Thu, 6 Oct 2005 08:26:57 -0400

On Oct 6, 2005, at 7:55 AM, Simon Liu wrote:

Is this the correct behaviour?  That changes made in different
contexts to a single store need to be saved in order for the changes
to be seen by all contexts (assuming they refresh the changed
objects)?

Yes - you must save for alternate contexts to be able to pick up the changes on refresh.

Jim

_______________________________________________
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


Follow-Ups:

Re: CoreData - NSManagedObjectContext notifications - Save vs	DidChange ?
From: Simon Liu <email@hidden>


References:  
  >CoreData - NSManagedObjectContext notifications - Save vs DidChange	? (From: Simon Liu <email@hidden>)
  >Re: CoreData - NSManagedObjectContext notifications - Save vs	DidChange	? (From: Chris Hanson <email@hidden>)
  >Re: CoreData - NSManagedObjectContext notifications - Save vs	DidChange ? (From: Simon Liu <email@hidden>)




Prev by Date:
Re: CoreData - NSManagedObjectContext notifications - Save vs	DidChange ?

Next by Date:
How to release Cocoa objects from Perl? (PerlObjCBridge or	CamelBones)

Previous by thread:
Re: CoreData - NSManagedObjectContext notifications - Save vs	DidChange ?

Next by thread:
Re: CoreData - NSManagedObjectContext notifications - Save vs	DidChange ?

Index(es):

Date
Thread