Looks like my first two posts fell through the cracks. Create a journal of changes on the server. Each journal entry should essentially be the SQL needed to apply the associate insert/update/ delete. Timestamp each journal entry.
When a phone syncs, have it pass the timestamp from it's previous sync. Have the server send all the journal entries since that time. Have the phone apply the updates and then update it's "last sync time" with the timestamp from the last journal entry sent. On Feb 22, 9: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
