Hello! I have an application that will try to access an sqlite database for some database operations such as selecting, deleting, inserting, and/or updating records. This application spawns some children that will also do the same transactions to the database. I have developed a locking mechanism that will lock the database file in a blocking mode to avoid sqlite_busy error. This mechanism actually works as expected. However, while the application is actually running, the database transactions returns sqlite_busy quite frequently in such a way that no transaction in all process can be processed. The database contains really a great number of records. Would this be a cause while an exclusive lock will be taken by sqlite itself?
I have read something that gave me a hint that the amount of records in the database will actually let sqlite get an exclusive lock. The url is: http://www.mail-archive.com/sqlite-users@sqlite.org/msg28643.html so you guys can check out for yourselves. If anyone can help me go around this problem, please do so. Thank you and God bless! Best regards, arbalest06 -- View this message in context: http://www.nabble.com/SQLITE_BUSY-frequent-error-tp17847439p17847439.html Sent from the SQLite mailing list archive at Nabble.com. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
