On 11/17/2009 05:32 AM, ext Israel Brewster wrote: > Simple (I hope) question here for my first posting to this list: > Running SQLite 3.4.0 on Mac OS X 10.5.8, should I or should I not be > able to place a SQLite database on a network share and have it work > for a single user? I know there could be issues if multiple people > tried accessing it at the same time, as well as potential performance > issues regardless, but I'm trying to find out definitively if it > should work at all - the idea is to have location portability, as > opposed to truly sharing the database. > > Actually, in my testing it works fine from the command line sqlite3 > client. The problem I am running into is that whenever I try using > sqlite through the Qt (http://www.trolltech.com/) sqlite driver, I get > an error indicating that the database is locked if the database file > is located on a network share (tried AFP and SMB). Now I know that > this sounds like a Qt problem, and in fact I believe that to be the > case. However, when I ask them about it, they stubbornly keep > insisting that it is a sqlite problem. As such, I wanted to at least > throw the question out to you guys to get your feedback. Could this > possibly be a SQLite problem? Or are the Trolltech/Qt people just not > willing to accept that the problem is with their driver? Thanks. > ----------------------------------------------- > Israel Brewster > Computer Support Technician II > Frontier Flying Service Inc. > 5245 Airport Industrial Rd > Fairbanks, AK 99709 > (907) 450-7250 x293 > ----------------------------------------------- > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > :P I'm watching here too. As I stated before, it's unlikely as we're using standard procedure, and nothing out of the ordinary at all. Add to the bug repo and we'll schedule it with the approx 120 other bugs against the SQL section and try to replicate. Nothing has changed significantly that would impact this in qt for a very long time now, (as well as the fact that we're performing a whole lot of autotests on a very regular basis). Have you tried opening up a debugger, and trying to see where the code's actually failing/returning SQLITE_BUSY to you?
-- Bill King, Software Engineer Qt Development Frameworks, Nokia Pty Ltd Brisbane Office _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
