Hi, this problem appear only in accessing the sqlite database from Mac OS X on a Windows shared disk. On full Windows networks and also on Mac OS X in local all runs fine.
I tried with the oplock enable and disable on the Window server but the Sqlite db always remains locked from the Mac. I have more than 97% of my customers that work stand-alone or in a network environment with less than 4 computer and I haven't any control on the hardware they use so I think the Sqlite solution is preferable instead of a client-server db. I have also some customers with 10-12 computer but due the kind of product there isn't an high concurrency in writing and tracking the locks it appears that only 4-5 locks/day for just 0.3 seconds each one executed on these bigger network. Marco -----Messaggio originale----- Da: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org] Per conto di Simon Slavin Inviato: domenica 12 dicembre 2010 20:38 A: General Discussion of SQLite Database Oggetto: Re: [sqlite] Lock problem opening a Sqlite db on a Samba/CIFS shared disk On 12 Dec 2010, at 7:09pm, Marco Turco wrote: > I am having a problem running my Window Sqlite app on Mac OS X with > Wine emulator. > > It runs well in local but when I try to access to a network disk > hosted on Windows XP The Wine emulator is an excellent emulator but it doesn't correctly emulate all the obscure elements of Windows. Please try it on a proper Windows computer. > I checked on internet about this and as I know Sqlite at this moment > doesn't support the Samba/CIFS disk with reference to the locking system. Sorry, I don't know. However if you have both Mac and Windows clients trying to access the database simultaneously, you should be very careful with your settings for oplocks and such things. Perhaps someone with experience of that kind of setup can help. > I am really in trouble because I have more than 50 customers with > mixed network (Windows/Mac OS X) having this problem in the next future. I know this is not what you asked but I have advice. If you have users with more than 5 or ten computers trying to access the database simultaneously, you may want to use a proper multi-user SQL engine instead of SQLite. If you use a SQL engine with client/server architecture no disk locking is done: the only computer actually accessing the database files is the server. I'm not saying that SQLite will fail, I'm saying that MySQL (and several similar systems) are specially designed for simultaneous multi-user access, and they do the job without having to worry about file locking and access from different types of computer. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
