Iphone data migration and app design
I am working on an application that comes with a read-only database.
The user will launch the application and will be able to select a series of "favorites" from the database, which will appear in the "favorites" section. That is, storing primary keys.
Each time the app is updated, the read-only data potentially contains more entries or has things like spelling fixes, etc.
I'm using Core Data, but I'm not sure if I should use it to store user favorites. Just like my way of thinking - it can be a headache for migration. Is this the case?
Should I consider storing the favorites in a plist and running some sort of query to retrieve the entries? Any recommendations?
Also what internals of the iphone app is kept (or can be kept) during the update?
I think that it is.
Thanks for any of your answers.
Cheers, Matt
source to share
I'm using Core Data, but I'm not sure if using it to store users' favorites as well. As - to my way of thinking - it can cause headaches for migration. Is this the case?
If you are going to port your application to another platform, then Core Data is not suitable. And since we're talking about a static database, I would keep it simple - read it once, do what you need to do, and close it and forget about it. Not like a real database where you do a few GETs and some additions, modifications, and deletions.
Should I consider storing the "favorites" in a plist perhaps and running some sort of query to retrieve the record? Any recommendations?
Your database can also be plist. After the user selects their favorites, you can easily save them to another plist. This file is located in the Documents or Prefs folder.
When a new app is released, you can probably compare your favorites to the new entries to correct any typos or other changes, if applicable.
And what internal chunks of the iphone application is kept (or can be kept) during the update?
I believe your application has been replaced, but the document and settings folders are preserved.
source to share