On Sun, 8 Jul 2012 13:22:42 -0400, C M wrote:
>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).
Unless you use things like
PRAGM
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
th
On Sun, Jul 1, 2012 at 12:12 PM, Simon Slavin wrote:
Thanks for the help. Sorry to not get back sooner.
>> 1) locked database (due to using SQLite Database Browser to change a
>> database but not Saving it)
>> 2) sqlite3.OperationalError: SQL logic error or missing database
>> (happens very rar
-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,
On 1 Jul 2012, at 3:36am, C M wrote:
> 1) locked database (due to using SQLite Database Browser to change a
> database but not Saving it)
> 2) sqlite3.OperationalError: SQL logic error or missing database
> (happens very rarely. No idea why)
> 3) sqlite3.OperationalError: disk I/O error (also h
I'm working on a database program and have found three different kinds
of SQLite errors now and then, only 1 of which is known as to what is
causing it:
1) locked database (due to using SQLite Database Browser to change a
database but not Saving it)
2) sqlite3.OperationalError: SQL logic error or
6 matches
Mail list logo
