Out of the many thousands of users, I've never had an SQLite datastore corruption problem reported to me, so I feel that it's quite robust.
On Aug 4, 11:39 am, gjs <[email protected]> wrote: > Hi, > > Easy answer is don't store you eggs in one basket, I use both sqlite & > xml for the same data, I used to find sqlite datastore was fairly > susceptible to corruption. xml makes it easier to restore the sqlite > database if needed, just a lot more work. > > Regards > > On Aug 4, 12:32 pm, Zsolt Vasvari <[email protected]> wrote: > > > > > > Your app should support older versions of the sdk without the user > > > having the revert to an old (outdated) version of your app. > > > If you are going to support older versions, you should do so by > > > keeping your latest versions backward-compatible. > > > However, sqlite should be fine for this job. > > > This sounds like some weird bug. > > > Of course, my app is backwards compatible. > > > > Anyway, what's "My Book #4" ? > > > Is that the name of the file of your database? > > > Yes. My app supports multiple independent databases called "Books." > > Books are to my app like .doc files to MS Word.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
