Re: Different context in Core Data
Re: Different context in Core Data
- Subject: Re: Different context in Core Data
- From: Jim Correia <email@hidden>
- Date: Mon, 17 Apr 2006 14:40:32 -0400
On Apr 17, 2006, at 2:19 PM, Matteo Manferdini wrote:
Hi everyone. I'm developing an application that uses Core Data. 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.
Putting them in different context keeps the data separated
conceptually and creates two different persisten stores
It doesn't. You can use multiple managed object contexts with a
single store (but you'll have to use the SQLite store if you do this.)
There are several reasons why you may want to use multiple managed
object contexts. Threading is one. Isolating edits in their own
"scratchpad" is another.
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