Core Data Design: better 1 model with 2 stores or 2 models and 2 stores?

Question

I'm facing a design problem using core data in an iOS app.
I've got two stores, one will contain a sort of catalog, the other only user data. I've read all those questions:

But what I still didn't get is if it is better two use one model on two persistent stores or two models merge them at runtime with two stores. What will be easier, eventually, to migrate?

Why do you need 2 stores ? I always have all my data in 1 store. — Dev2rights, Apr 28 '13 at 16:59
http://stackoverflow.com/questions/10374796/why-might-i-want-2-or-more-core-data-models — Andrea, Apr 29 '13 at 06:13

score 2 · Accepted Answer · edited Apr 30 '13 at 17:13

2

The definite way to go here is have one data model with two stores, administered via two so-called configurations.

In the model editor you can define which entities belong to which configuration.

In code you specify the identifier string of each configuration when adding the persistent store.

See the WWDC 2012 video on Core Data and iCloud that explains it really well.

edited Apr 30 '13 at 17:13

Martin R

529,903
94
1,240
1,382

answered Apr 28 '13 at 20:10

Mundi

79,884
17
117
140

Core Data Design: better 1 model with 2 stores or 2 models and 2 stores?

1 Answers1