question about sqlite DB

[srpblitz]

if i create a database and build an app around it and then when uploading the finished app are you allowed to include this database as a separate file that gets installed say on the iphone along with the app itself. Trying to make sure my design concept is doable. The standalone database would then sit on the iphone as persistent storage whenever app is started and could grow to the theretical limits of disk storage available on phone. Am i correct in this concept? Then if i submit update for app how do i keep from overlaying database?

[nobre84]

Originally Posted by srpblitz

if i create a database and build an app around it and then when uploading the finished app are you allowed to include this database as a separate file that gets installed say on the iphone along with the app itself. Trying to make sure my design concept is doable. The standalone database would then sit on the iphone as persistent storage whenever app is started and could grow to the theretical limits of disk storage available on phone. Am i correct in this concept? Then if i submit update for app how do i keep from overlaying database?

You can include your db inside the App`s bundle, for a read-only database. You may copy it to your application`s Documents directory once installed, and change the data as you wish there. When updating your app you should verify if there is any data previously available and keep it.

[srpblitz]

Originally Posted by nobre84

You can include your db inside the App`s bundle, for a read-only database. You may copy it to your application`s Documents directory once installed, and change the data as you wish there. When updating your app you should verify if there is any data previously available and keep it.

Thanks for the reply. I wanted the db to be updatable by app when installed on iphone so im curious about why you say read only. Also, by having db that user saves data into does that mean the app is now responsible for db maintenance like for when space runs out? Liability implications? Not sure i want to add a maintenance nightmare.

[nobre84]

I mean, the database you ship inside your bundle (the .APP directory) cannot be written. You must make a copy to a writeable directory on your application sandbox (/Documents). So, in fact when you update the app, only the Bundle will replace the older one, the previous work database is in the Documents directory. You need then to compare them and act appropriately

[srpblitz]

Okay, I think i'm following, I just don't know the semantics of file creation on these devices. I want to create a database where the user can save data while using app but I don't want to wipe out that database during app updates but I do want the user to be responsible for their own database and data after initial creation. I simply provide option to add/update/delete.