On 7 Jan 2013, at 1:16pm, Raymond Meester <[email protected]> wrote:
> 1) What is the best way to use sqlite on a networkshare (shared cache > mode / unlock notify / busy timeout etc)? I saw a lot of posts about issues > with > multiple connections when the db file is on networkshare, but for some > it seemed to work ok. > 2) Will there be an alternative locking mechanism to keep the database > concurrent without relying on file locking on OS level? (or somehow a > workaround > like forcefully unlock the db or using semaphores). Not everyone has > access to a server, so I think there's still a use case for this. The problem is that the various facilities provided by various operating systems and network file systems for file locking cannot be relied on. Very often, once you investigate exactly how they are implemented you find that the locking routines are not implemented at all. This is true for various versions of both Windows and Unix, for various network file systems like SMB. SQLite does call operating system routines the documentation says are for locking. If the operating system works properly SQLite will work. But it doesn't. > 3) Are there plans for a built in server mode (if 2 is not an option), > instead of relying on a third-party or custom implementations? I don't think you'll ever see a server mode built into SQLite. It would have to work with far too many different operating systems and file systems and with too many different modes depending on how the programmer wants arbitration to work. Programmers are encouraged to create their own little servers and server protocols which solve just the very small range of things their application needs to do. Simon. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
