Calling SQLite database to update UITableView.

Question

Hi!
I've been asking lately about Obj-C circular buffer objects, assuming that would be the better way to control tons of data on a UITableView.
I have found a solution as far as Circular buffer objects go, but I've been wondering about maybe a better, faster and much more memory efficient solution: Calling my SQLite DB to update the UITableView.
In a way - the memory will be released after updating the UITableView, and there won't be any need to hold reference to the objects, which will be more efficient and memory saving than holding a constant NSMutableArray with all of the objects inside it.

How would you approach updating a UITableView with masses of data (50k objects) that are also stored on a SQLite database?

Thanks in advance, ~ Natanavra.

Answer 1

What you are describing is exactly what NSFetchedResultsController was designed for, and is one of the huge advantages of using Core Data on the iPhone. With NSFetchedResultsController, you can set up a fetch request from your database for the elements to be displayed in your table view, and limit the batch size of items to be loaded at any given time. This significantly reduces memory consumption and loading time (I've seen 8X improvements in loading time in specific examples).

NSFetchedResultsController was designed to be integrated with a UITableView. For specific examples, I'd consult Apple's sample code, such as their CoreDataBooks one, as well as the appropriate sections in Marcus Zarra's Core Data book and the Pragmatic Programmers' iPhone SDK Development book. Both of those books have very good explanations of the core concepts.