Hi, What Simon is right.
When solving a similar problem in the past I created special tables in both databases which i filled from triggers on the data tables. These tables contained the changed data which i then could reproduce on the other database using a special deamon process. However, my application logic was such that conflicts (like the one Simon described) could not occur. None of these databases was sqlite, by the way. Martin Simon Slavin wrote: > On 8 Jun 2009, at 7:30pm, Mohey Eldin Hamdy wrote: > > >> I am trying to synchronize an sqlite local data base with a remote >> mssql >> data base. I wasn't able to find any listed function at >> http://www.sqlite.org/c3ref/funclist.html to do something like that. >> Any >> ideas please. >> > > > The sqlite3 library would not have functions to access MSSQL > databases. But that's the least of your problems. > > Synchronising two copies of a database is a whole twisty basket of > fish. Very difficult to program and complicated to keep running. > Consider what happens if one user deletes a record from their copy of > the database and then the other user updates the record in theirs. > Synchronisation would have to be done at the application level anyway, > not in the library. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
