> Ignoring SQLite, I would never expect to be able to go back to an older > version of *anything* and have it read the same data files created by a > newer version.
Why not? If the app version is the same, and the app otherwise supports various SDK levels, the user should certainly have the option to switch between devices running the various versions. > If your application were writing its own data files, do you think it would > robustly be able to read ones written by a newer application in an older > version of it? The app version the same, so you are talking about a different scenario. Of course, I wouldn't expect my app to be forward compatible. > In terms of SQLite specifically, I also wouldn't consider this a document > storage mechanism. It is a database, and good for that kind of stuff, but > if you have data you want to transport across different devices I really > think it should be in a robustly designed document format. Ideally, yes, but since the database is just a single file, ideally it should suffice to be the "document format." But, to solve this issue, I will have to bite the bullet and probbably turn my database into a giant JSON document. -- 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
