On Feb 15, 2013, at 4:21 PM, Jens Alfke wrote: > On Feb 15, 2013, at 8:11 AM, Keary Suska <cocoa-...@esoteritech.com> wrote: > >> If what you are looking for are the benefits of Core Data but with your own >> database back-end, you pretty much will have to write your own database >> coordination methods, as well as change tracking and undo >> management0--essentially everything that NSManagedObjectContext does. > > Isn’t this what subclassing NSIncrementalStore is for? Creating your own > back-ends for CoreData?
I forgot about that. I didn't take that approach for number of reasons, mostly due to when the system was mostly written and the OSes I had to target, but it will work except for issues that are the continuing limitations of Core Data, in particular ACID compliance of any kind. In my case I am working with a multi-user back-end and a complex schema so I need predictable locking and transactional semantics (especially nested transactions). Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
