Mikhail Gusarov wrote:
Seems so. Does problem disapper after installing python-pysqlite2?
Gerfried Fuchs wrote:
No, but that dependency is indeed missing.
Is the python2.5 package installed with the "sqlite3" module? That
module was not previously (<= 2.4) distributed with Python but had to be
installed separately (python-pysqlite2?). Apart from the difference how
these modules are being distributed, the only other difference that I am
aware of is how they are imported:
* import sqlite3 # This is what clive uses
* from pysqlite2 import dbapi2 as sqlite
So with this in mind I don't think that the python-pysqlite2 is
required. Perhaps someone who's more familiar with Debian Python
packages could give a better answer.
Gerfried Fuchs wrote:
python-pysqlite2 2.4.1-1 Python interface to SQLite 3
I think that package depends on libsqlite3-0 (>= 3.4.2) so it's probably
safe to assume:
"After ADD COLUMN has been run on a database, that database will not be
readable by SQLite version 3.1.3 and earlier." --
http://www.sqlite.org/lang_altertable.html
Is not the reason. There must be something wrong in src/clive/cache.py:
Cache::_upgrade_if_needed method.
Unfortunately I haven't been able to reproduce this bug yet, so until
the culprit is found, the quick fix is to remove the cache file manually
or disable the caching altogether.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
