Question regarding ideal database implementation for iPhone app

Posted by Jeff on Stack Overflow See other posts from Stack Overflow or by Jeff
Published on 2010-06-14T18:41:19Z Indexed on 2010/06/14 18:52 UTC
Read the original article Hit count: 276

So I have a question about the ideal setup for an app I am getting ready to build. The app is basically going to be a memorization tool and I already have an sqlite database full of content that I will be using for the app.

The user will navigate through the contents of the database(using the uipickerview), and select something for memorization. If that row or cell of data is selected, it is put into a pool or a uitableview that is dedicated to showing which items you have in your "need to memorize" pool. When you go to that tableview, you can select the row, and the actual data would be populated. All information in the tableview would be deletable, in the event that they don't want it there anymore...

Thats it.

I know that with database interfacing, there are a few different options out there, in this particular setup, is core data the easiest approach? Is there any other way that would be better? I am just kind of looking for a point in the right direction, any help is greatly appreciated!!

© Stack Overflow or respective owner

Related posts about iphone

Related posts about sqlite