Very large NSDictionary vs Core Data vs SQLite to view only on iPhone?

Question

I fiddled with the iPhone application, where I use the DAWG structure to search for anagrams from a user word bank in real time as the user enters. This part works well. When the words are identified, I want to get specific information about each word that I have in the plist file (with a key by word). This information must be imported and accessible at application startup.

On startup, I can easily prepare plist for an NSDictionary object using initWithContentsOfFile, but this creates a dictionary with ~ 200,000 key / value pairs. I guess this is not the best approach, as plxt files in txt, bin and xml format are 2.8 MB, 3.9 MB and 7.5 MB, respectively.

Should I use Core Data or SQLite? My main priority is productivity, as I would like to find information for literally tens of thousands of results in real time, when the user will be, if possible, whenever possible.

thank

Answer 1

, ( Instru.app). , , , , . , , , NSDictionary . Core Data, . SQLite , - , .

Answer 2

Sqlite , . , - 3/4 . , , dbs.

-e.sqlite -l.sqlite -z.sqlite

select, db.