>I will have to say very sadly that if you absolutely have to have a >system where the DB file is not on the exact same machine (physical) >than the client software (the bit using SQLite code), then SQLite is not >a good choice - consider MySQL or Postgres perhaps. There was a crowd >some time ago making an SQLite for client-server environments >(SQLitening if memory serves), but I believe it's a commercial system. >See: http://www.sqlite.org/whentouse.html
QNX also modifies SQLite (QDB) to work with their distributed interprocess messaging, thus all operations, even from remote nodes, occur against a local filesystem ... or at least that was the case last time I looked at it. --- Theory is when you know everything but nothing works. Practice is when everything works but no one knows why. Sometimes theory and practice are combined: nothing works and no one knows why.
