A simple thing to prevent data collisions is to design a unique name for each client into the tables. That way you know where the data comes from.
--- On Mon, 4/20/09, Ravi Thapliyal <[email protected]> wrote: > From: Ravi Thapliyal <[email protected]> > Subject: [sqlite] How to synchronize the SQLite db - SQLite db > To: [email protected] > Date: Monday, April 20, 2009, 2:34 AM > I am looking at a design that will > require synchronizing a disconnected > SQLite DB file on client's machines to a central server. > The version of the DB on the server will also be modified > periodically, so > there is a chance that new records will be created in > either and also > updated. > Conflicts therefore are an issue. What I'm worried about is > just the > logistics of either > 1) Importing all user's data to a single > DB somehow > 2) Managing several DB files from clients > automatically. > 3) Has anyone does this kind of syncing? > I realize I'm somewhat light > on details, but I'm not really even sure exactly what this > system will need > to do: it's more of a framework really. > At any rate, anyone have experience synchronizing SQLite > DB files? > Suggestions appreciated. > > -----Inline Attachment Follows----- > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
