Hi David,
Regarding: "What are the recommended "best practices" around using SQLite in a distributed scenario?" [two-phase commit, etc.] I trust that someone with some actual relevant knowledge will reply to your query later, but I imagine that many would say the the "recommend best practice" is *not* to use sqlite, since sqlite was designed to be an elegant embedded database -- without even one server -- let alone multiple synchronized ones. I take it you have strong reasons for rejecting, say, Postgres, which now implements two-phase commmit right out of the box? http://www.postgresql.org/docs/current/static/sql-prepare-transaction.ht ml You may already know everything in articles such as this one http://en.wikipedia.org/wiki/Two_phase_commit#Distributed_two-phase_comm it_protocol And its references (I don't claim to), but I'm listing it here just it case it's helpful to you. On the other hand, if you *do* develop a solid "distributed sqlite" implementation, I'm sure others would be interested. Regards, Donald Griggs This email and any attachments have been scanned for known viruses using multiple scanners. We believe that this email and any attachments are virus free, however the recipient must take full responsibility for virus checking. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
