Following the advice in
http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdPerformance.html#//apple_ref/doc/uid/TP40003468-SW5
regarding storage of BLOBs, I've chosen to store binary data for my
NSPersistenDocument-based app (Leopard-only, if that makes a
difference) in
On Jan 16, 2009, at 10:00, Barry Wark wrote:
I would like to encapsulate the management of this external file in
the model-related classes since I will need the same functionality
during schema migration. Thus managing the external data file in my
NSPersistentDocument's subclass seems wrong.
On Fri, Jan 16, 2009 at 3:00 PM, Quincey Morris
quinceymor...@earthlink.net wrote:
On Jan 16, 2009, at 10:00, Barry Wark wrote:
I would like to encapsulate the management of this external file in
the model-related classes since I will need the same functionality
during schema migration. Thus
On Jan 16, 2009, at 17:26, Barry Wark wrote:
In fact, that's how I started. It works fine (using a separate entity
for the data), and performance was fine. Unfortunately, the backup
system at the deployment site backs up entire changed files (rather
than binary diffs), so the continuous changes
