On 11/12/08 11:27 AM, Todd Blanchard said: >I'm working with another developer on an app with a rather elaborate >core data schema. We are each working on different parts of the >schema. Having one model just isn't scaling - version control does >not like model files - they constantly get broken and are a nightmare >to merge. > >Is it possible to have multiple model files that share some entities? >Is there code to stitch them together at compile time into one >compiled model file? > >This is a serious scalability issue for us. We might as well not >have the thing in version control at all since we have to agree who >owns the file at any one time to keep from messing it up.
Have you read the NSManagedObjectModel docs? +modelByMergingModels may help. You could ever forgo .xcdatamodel entirely and build your model in code. I'd just bite the bullet for now, when your model is in flux at the beginning of design in sucks, but your model will stabilise eventually. Do file a bug requesting that the .xcdatamodel become text (just like the nib -> xib change), and mergeable text at that (unlike .xib). -- ____________________________________________________________ Sean McBride, B. Eng [EMAIL PROTECTED] Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
