I received a task to investigate feasibility of using sqlite database located on a server in an internal windows network.
I know this is not most recommended scenario but I still have to do investigation. Let us assume this case: 2 machines are accessing sqlite database located on a third machine in shared folder with full read/write permissions. At some point in time both machines want to access database for writing some data in teh same table. One machine request comes first and table is locked. Therefore the other machine receives error, or goes to wait timeout period before trying again. Locking and releasing is done by 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. Is there a way to detect this situation and what would be the remedy? Please do not respond me with use client/server database. This investigation is only related to sqlite usage. Thanks in advance, Darko Miletic _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
