I’ve been struggling to find an answer to a problem I’ve currently got to solve.
I’ve developed an iphone app (and a mac app for data entry) that both use the same datamodel.
I can create data in the mac app, save it as a sqlite file, and load it into my iphone app. That works fine.
The sqlite database contains mostly “read only” data that will be updated - new records, fix spelling mistakes that kind of thing - with each new app release. So the “model” won’t be changing, only the “data”.
The end user will also be able to select records from the “read only” data and add them as “favourites” together with some basic details.
So for the first release everything will be easy. However I haven’t figured out how to handle the “subsequent” releases yet.
What would be your “best practice” suggestion to solve this?
Obviously I won’t be able to simply replace the database entirely - with each update - due to the users “favourites”.
Thanks in advance, Matt
PS: It could be worth mentioning a solution to this kind of problem in your book perhaps?