> server machine actually per request from cient. Now if, for some reason, > connection with machine taht started writing table goes awol. That > client finished his job or is just dead but server still thinks > connection is needed and keeps file locked hence preventing any other > client to do reading/writing.
Though I haven't tested it, I would hope that the O/S would detect that the client disconnected, and would release any file lock(s) held. Seems like it would be easy enough to test: On a couple of machines, start a couple of SQLite command shells to the shared Db. On the first, start a BEGIN IMMEDIATE;, then yank the ethernet plug. See if the OS eventually releases the lock, such that the second client can get access. I'm sure others have more experience with this. But it seems like it would be easy enough to test. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
