Greetings, I'm working on a small win32 application that periodically writes data to a SQLite database located on a remote machine, the remote database file is opened with a UNC file name, e.g. \\remotemachine\share\path\to\db
Now if the remote server that holds the database file gets shut down or rebooted while my application still has an open DB handle, then the next DB operation will cause my app to get stuck in the busy_handler, apparently thinking the DB is locked. Is this intended behavior or a bug? As a workaround I'm now checking if the file exists each time the busy handler gets called, and aborting the operation if the file is no longer there. If anyone knows of a better way to handle this situation, please let me know :) ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
