I think this is not a good idea for most of the applications, because sync online to offline -> work on offline db -> backup offline db -> more work on offline -> sync offline to online -> restore offline -> resync to online => big mess.
Right now you can save the DB file somewhere else. It is a normal sqlite DB that can be browse/accessed locally with any sql browser. And is not "hidden" from user: http://code.google.com/apis/gears/api_database.html#ResultSet-fieldByName see Location of Database File On Aug 29, 9:21 pm, "gal.gefen" <[email protected]> wrote: > I am writing a web application that can run completely offline (never > communicate with the server), but uses the Gears database. > > I must allow the user to backup the data (and possibly restore it), > but Gears hides the database from the user. > > I would think there should be > > 1) an option in the tools->Gears settings menu to backup/restore a db. > 2) a method in the API that allows to get the db location (so I can > ask the user to copy it) + a specification of what will allow a > correct restore. > > Does anyone else needs this ? > Any advice what to do right now for backup ?
