The issue of locking a file during concurrent access seems to be a major issue, mostly due to the schizophrenic abilities of network file systems. Has the SQLite development team considered embedding its own file locking system logic, such as creating its own lock file to prevent damage from concurrent write access, that does not rely on the network file system? Seems that if the issue is due to the design of the network file system, which we have no control, then embedding some internal logic system that handles self-flagging of a lock condition seems a reasonable course to pursue.
------------ Scott Doctor scott at scottdoctor.com ------------------
