Different context in Core Data
Different context in Core Data
- Subject: Different context in Core Data
- From: Matteo Manferdini <email@hidden>
- Date: Mon, 17 Apr 2006 20:19:33 +0200
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, but has the
drawback that if I will need to link conceptually these data via
relationships in future releases, I will have to re-architect the
data model and maybe the application (not counting that I will have
to provide compatibility with old data). My problem is that I don't
see the benefits related to one choice or the other.
Thank you for all your support, this mailing list is very useful to me!
Cheers.
---
Matteo Manferdini
_______________________________________________
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