Thanks for the help, just getting back now. > Your message indicates you are using Python. You should be using > transactions and context managers. This ensures that things either > complete or don't, not some half way state.
I thought SQlite never did anything in a half way state anyway? I thought that if something failed to be written it was rolled back? (Pardon if I'm mangling the terminology or misunderstanding it badly). > Finally you should have a test suite for your code. The good news is that > it is fairly easy to cause some of the errors. For example if you would > like a database to be locked then open it in a new connection and execute > "BEGIN EXCLUSIVE". Any idea how to produce the other errors? Like the Disk I/O error given by Python's sqlite3 module? Thanks again, Che _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
