vishnu wrote: > Hi, > Im currently using 0.9.2 version SQLObject in my CentOS5.1 system. > > Im using SQLObject in a multi-threaded application. I have my own mutex > lock to prevent more than one write operation. No restrictions in > application for Read operation.
Why can't you let the database server take care of locking things as needed? I have applications used by multiple users in multiple processes (web) and the database does all what is needed. It really feels like if there were several desktop applications and all of them worked simultaneously. > My problem is that i get occational "Database is locked error". > > Im not sure as to the cause of this issue. is there a way to give a > timeout to wait for lock release. It should probably be a problem in your locking mechanism... > I dont find any help in SQLObject site about any syntax on timeout Google give some hints of using other modules to have this implemented. But I still believe that it would be better to let the database handle that. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
