Leaks with Core-Data while fetching data
Leaks with Core-Data while fetching data
- Subject: Leaks with Core-Data while fetching data
- From: "Hell's KItchen Hell's KItchen" <email@hidden>
- Date: Sun, 6 May 2007 18:20:35 +0200
You might also want to consider separating the downloading of messages
from the linking of messages together. Doing a fetch per message
downloaded is very inefficient; you'll likely be better off putting
off the linking to a separate stage, after you have all of the
messages downloaded. That will allow you to have more flexibility in
how you structure the fetch, for example; you could fetch all messages
that you want to link to message 1234 at once, for example, rather
than performing that fetch N times, once for each message that links
to message 1234.
Well this mean that I should to download all messages (it can be
easily > 3000), keep it into the memory and then, when the download is
finished, write the entire text into the Data file (it contains all
articles) and link the messages together into the Index File
(Core-Data Persistent Store, it contains the range where you can found
the entire text of the messages, the index itself contains all usefull
infos to show in nstable).
Ok I could be a solution but...
a) you should mantain an NSArray of messages (or eventually only the
necessary infos that I'll store into core-data framework). It should
be consume memory....or not?!
b) the write process to persistent store-sql- could take a while (I
haven't tried with 3000+ indexes but I've read that the coredata
engine it's not so fast).
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden