-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30/06/12 19:36, C M wrote: > So, because these errors, if not handled, lock up my application,
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. http://pysqlite.readthedocs.org/en/latest/sqlite3.html#using-the-connection-as-a-context-manager The errors always turn into exceptions. You should follow best practises. http://docs.python.org/howto/doanddont.html#except http://eli.thegreenplace.net/2008/08/21/robust-exception-handling/ http://www.doughellmann.com/articles/how-tos/python-exception-handling/index.html 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". Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/whmUACgkQmOOfHg372QRYKACgjJ3INXrOuo4caLlFBI246Dz0 KpIAniQwiHYAFhHgI8BotWYhdsrh04hr =nQK1 -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
