Lists

Open Menu Close Menu

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

Re: Different context in Core Data

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

Re: Different context in Core Data

Subject: Re: Different context in Core Data
From: mmalcolm crawford <email@hidden>
Date: Mon, 17 Apr 2006 11:41:18 -0700

On Apr 17, 2006, at 11:19 AM, Matteo Manferdini wrote:

I have data that can be divided into two different conceptual disjoint sets, so I was wondering if it's better to put them into two different managed object contexts or not. Core Data programming guide does not explain what are the points of the two choices.

The role of a managed object context is to provide a "scratch pad" -- precisely to allow you to keep different conceptual disjoint sets of edits...

(See, for example, <http://developer.apple.com/documentation/Cocoa/ Conceptual/CoreData/Articles/cdChangeManagement.html#//apple_ref/doc/ uid/TP30001201-185297-TPXREF149>.)

Putting them in different context keeps the data separated conceptually and creates two different persisten stores,

No, it doesn't.  It's not clear why you would believe this?

mmalc

_______________________________________________
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



References:  
  >Different context in Core Data (From: Matteo Manferdini <email@hidden>)




Prev by Date:
Re: Different context in Core Data

Next by Date:
Re: addObserver:forKeyPath:options:context

Previous by thread:
Re: Different context in Core Data

Next by thread:
Choose an NSFont with specific line height?

Index(es):

Date
Thread