CoreData and plugins
CoreData and plugins
- Subject: CoreData and plugins
- From: Dave Hayden <email@hidden>
- Date: Thu, 1 Dec 2005 18:10:04 -0800
I've been playing around with CoreData for the last few days, trying
to find if there's any way to let app plugins extend the data model
in a reasonable way. So far, it's looking pretty ugly. I'd hoped that
using different SQLite stores for each plugin would let me load
stores for only the plugins available and add new models for new
plugins. Unfortunately, it looks like NSPersistentStoreCoordinator
requires each SQLite store to match the entire model exactly, even
for tables it doesn't use; adding a new entity to the model
invalidates all existing stores, even though it really only requires
adding the right tables. Is this correct, or am I missing something?
Is there any way to use existing stores in an extended model short of
hacking the SQLite schema by hand?
Or does someone have a better solution for using CoreData in a plugin-
able application?
Thanks!
-Dave
Panic, Inc.
_______________________________________________
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