Just a follow up. I tried to reproduce this bug on systems with:
  * sqlite-3.5.6; python-2.5.2
  * sqlite-3.4.2; python-2.5.2

I used:
  * clive-0.4.7
  * clive-0.4.9

To create a database (~/.clive/cache) without the "cache_lowq" column which was added in clive-0.4.10.

I then tried to get Python to raise the OperationalError with:
  * clive-0.4.11

Which did not occur. clive-0.4.11 upgraded the database everytime as it was supposed to.

I'll look into adding a safeguard for the OperationalError in clive-0.4.12 which will cause clive to reset the cache automagically.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to