No,you just have to log the bound parameters and a reference to the prepared statement (so the other side will know which statement to prepare). Or just log the statement & the parameters each time.
-----Original Message----- From: sqlite-users-bounces at mailinglists.sqlite.org [mailto:[email protected]] On Behalf Of Jim Morris Sent: Freitag, 06. Mai 2016 20:14 To: sqlite-users at mailinglists.sqlite.org Subject: Re: [sqlite] Incremental backup/sync facility? Doesn't this eliminate the use of prepared statements? On 5/6/2016 11:10 AM, Jeffrey Mattox wrote: > As an aside, this is how Apple syncs Core Data to iCloud (and then to > multiple iOS devices) if the backing store uses SQLite (the default). When a > small amount of data changes (which is common), the changes get send out, not > the entire (mostly unchanged and potential huge) database. > > Jeff > > >> On May 6, 2016, at 7:43 AM, Simon Slavin <slavins at bigfraud.org> wrote: >> >> Believe it or not, the fastest way to synchronise the databases is not to >> synchronise the databases. Instead you keep a log of the instructions used >> to modify the database. You might, for example, modify the library that you >> use for INSERT, DELETE and UPDATE commands to execute those commands and >> also save the command to another 'commandLog' table > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users at mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users ___________________________________________ Gunter Hick Software Engineer Scientific Games International GmbH FN 157284 a, HG Wien Klitschgasse 2-4, A-1130 Vienna, Austria Tel: +43 1 80100 0 E-Mail: hick at scigames.at This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is confidential, privileged or legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.
