Re: Progmatically Caching Objects from a CoreData SQLite Store?
Re: Progmatically Caching Objects from a CoreData SQLite Store?
- Subject: Re: Progmatically Caching Objects from a CoreData SQLite Store?
- From: Matt Neuburg <email@hidden>
- Date: Sat, 25 Feb 2006 09:07:05 -0800
- Thread-topic: Progmatically Caching Objects from a CoreData SQLite Store?
On Fri, 24 Feb 2006 16:54:32 -0800, Colin Cornaby <email@hidden>
said:
>
>On Feb 24, 2006, at 2:13 PM, Chris Hanson wrote:
>
>> For example, if you're storing images or large amounts of text in
>> attributes, these should be split out into their own entity and
>> related to the original entity instead.
>
>This right here was the problem. Split the binary data out into
>separate entities and there has been a drastic performance increase.
>I thought CoreData would load the object graph and create
>representations but I didn't know it would pull each attribute when
>it created the managed object (I thought that was pulled as needed).
>Thanks for the pointer.
Am I right in assuming (totally without testing, so it's truly just an
assumption) that this model change will *not* help if the store is XML
rather than SQLite? Thx - m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
_______________________________________________
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