JSON works good too. I have apps with 40,000+ items and I am n0ot caching them... I do realtime queries of the database on the server and return the results in a json file... it's not that slow especially if you are using threads and incrementally paging the results. It takes no time to pull enough results to fill the device screen.
Shawn On Feb 22, 10:47 am, feeder1803 <[email protected]> wrote: > Hi! I am starting to work with Android and SQLite and I have some > doubts regarding the database update. I have a SQLite database in my > application with a supermarket catalog. As the catalog doesn't change > a lot, I would like to update it from a webserver that I own. The > problem is that I am not really sure of how to do it with the maximum > performance. > > I don't want to download the whole database because it would be too > big, I've thought of placing an xml file in the server with the > registers that have changed and the new values to download it and > parse it on the phone generating SQL queries to update, delete or > insert. > > Another approach woul be updating the app but I think this would be > slower as it would download the whole database. > > Any ideas? -- 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
