The types of Core Data stores currently available are XML, SQLite, Custom Atomic, and In Memory (which must be binary) on Wikipedia.

The XML store is best used for debugging since it's just a text file that is human readable. It could be used for storing small amounts of data, but it would be far too slow for storing the web, PDF, and image data that Yojimbo is capable of.

The In Memory store would solve your large Time Machine backups since none of your data would be backed up (since all your Yojimbo data would be in RAM), but every time you quit Yojimbo you'd lose all your data. Again, not a good choice.

The downside of the Custom Atomic store (and also the XML format) is that by atomic Apple means that every time a change is saved to the Core Data store, the entire object graph is rewritten to the store. Again, for large Yojimbo databases this would be impractical.

SQLite offers MUCH better performance than XML or a Custom Atomic store, and also offers partial updates so when something is added, removed, or changed in your Yojimbo library the entire object graph doesn't have to be rewritten to disk, only what has changed.

With how cheap disk space is these days, I'd rather the developers at Bare Bones focus on adding more great features instead of writing a custom Core Data store or worry about storing Yojimbo items as individual files.

- Steve

On Apr 5, 2008, at 7:19 PM, Doug Ransom wrote:
"Core Data can serialize objects into XML, Binary, or SQLite for storage. With the release of Mac OS X 10.5 Leopard, developers can also create their own custom atomic store types. ". Any application to the problem at hand?

Steven Huey Software -

This message is sent to you because you are subscribed to
 the mailing list <>.
To unsubscribe, send mail to: <[EMAIL PROTECTED]>
List archives:  <>
Have a feature request, or not sure if the software's working correctly? Please send mail to: <[EMAIL PROTECTED]>

Reply via email to