This appears to have been asked many times online, but none of the threads I've seen help me fix my issue.
I am using SQLite through Python 2.5 or 2.7, which is the sqlite3 module. In a desktop application, every now and then, and in a fairly irreproducible way, when committing to the database I get this error: sqlite3.OperationalError: SQL logic error or missing database I thought this was a PySqlite generated error, but now I see the same error is seen with Ruby, PHP, C++ and other languages, so now it seems it is generated by SQLite itself...but I really don't know. If I try additional times in that same instance of my app being open, it gives me the same error every time. If I close the app and re-open it, it probably will not give me this error, with the same or very similar data being written in the same routines. So I "know" that the code as written is correct (a significant--greater than 90%?--of the time I don't see this error). In terms of what is causing this, I don't know, but I've noticed that on the occasions that this has happened my computer's RAM was pretty bogged down. I am testing all this on a 2004 laptop with a very fragmented HD with 1 GB of RAM, and I had the following processes running with this much RAM consumed: - Firefox.exe: 297,000 K (and climbing...This is FF 17) - plugin-container.exe: 51,260K. - Dropbox.exe: 30,212 K. - explorer.exe: 22,836 K - pythonw.exe: 18,432 K - svchost.exe: 16,992 K - notepad.exe: 5,532 K - and others... When there is this much RAM being used, particularly when FF is hogging it like that, my computer gets quite slow to respond to any action, such as saving a file (sometimes taking more than 10 seconds to return responsiveness). Is it possible that the "SQL logic error or missing database" error is due to the issue of low available RAM? Or the fragmented HD? Or something like that? (I get the impression from reading online that this is a very general error that could be due to just about anything, and as such gives just about no information). The problem is, I am currently sitting with FF over 400,000 K and I just successfully used my app, so it truly is intermittent. This error might go away if I used a newer/cleaner/more RAM computer, but I want to "stress test" my application for those who may be using similarly clunky computers--I want to try to avoid it even for older model computers. Any advice appreciated. _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
