Re: CoreData performance issues
Re: CoreData performance issues
- Subject: Re: CoreData performance issues
- From: Scott Stevenson <email@hidden>
- Date: Tue, 21 Jun 2005 23:47:43 -0700
On Jun 21, 2005, at 10:36 PM, Tomek Piatek wrote:
That is exactly what we're doing. I'm not sure if you're familiar
with Perl's Class::DBI modules. In a way they are similar to
CoreData. Class::DBI contains a convenience method called
"find_or_create". We use it all the time for this sort of thing
with no adverse effects. Typically we develop against MySQL.
DBI is an API wrapper with mostly static interactions. Core Data is a
dynamic persistence and change tracking system. In other words,
they're completely different.
To solve this, you can create a separate in-memory SQLite instance
using the SQLite C API (completely separate from Core Data, now),
that keeps all of the unique IDs of the imported objects in a very
simple two or three-column table.
Searching this will probably be much faster than building and running
a fetch request, and I think it's likely to be faster than
NSDictionary too. This is closer to the implementation that you're
used to with DBI.
- Scott
--
http://theocacao.com/
feed://theocacao.com/index.rss
_______________________________________________
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