what about to use a unique identifier for each row?but a unique identifier like UUID in sqlserver or Quuid in Qt? as it is unique over the world it could be enough?
at the worst case, prefix an id by the name of your machine if you have only 2 machines. then merge the records together? cheers, Sylvain On Sun, Jul 12, 2009 at 2:56 PM, Simon Slavin <slav...@hearsay.demon.co.uk>wrote: > > On 11 Jul 2009, at 8:03am, raf wrote: > > > you could also send individual sql statements via email but > > email doesn't always arrive. that is a major problem. you > > would need an acknowledgement and retry mechanism. perhaps > > there's an april fool's RFC for implementing TCP/IP via email :) > > > > once you've got that sorted, you'll need to make sure > > that the updates are digitally signed and probably encrypted > > and verify the signatures at the recipient's end. > > > > and i'm only half joking :-) > > Well of course you're joking. It's blatantly obvious that the correct > transport protocol for SQL messages would be an RSS feed. Although > come to think of it, you could Tweet them. > > 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
