Hi,
Am Sun, 14 Aug 2005 20:33:55 +0200 schrieb Ed Leafe <[EMAIL PROTECTED]>:
On Sunday 14 August 2005 13:53, Adi J. Sieker wrote:
[snip]
You're absolutely correct - I've made that fix, and posted the change
to the
Subversion repository. Thanks for catching that!
my pleasure. :)
Also should the SQLite backend work?
No. We thought we had someone who was going to be working on getting
this to
work, but they never came through. If you'd like to work on getting
SQLite
working, that would be fantastic! I'm not experienced in working with
that
product - is there a dbapi-2 compliant interface for SQLite?
I worked a little bit on it this morning in the train.
cur.description is not of type list when the result set is empty.
When I try add the method massageDescription to dbSQLite
and do this:
if c.description == None: c.description = []
I get a read-only attribute exception. So I'm a little
bit at a loss on where to go from here.
Also how to best handle this situation or is it even needed?
From the pysqlite documentation:
1. Python Database API 2.0 Compliance
1.1 Incompatibilities
No type information in cursor.description
cursor.description has a tuple with the fields (name, type_code,
display_size, internal_size, precision, scale, null_ok) for each column
that a query returns. The DB-API spec requires that at least name and
type_code are filled, but at the time cursor.description is built,
pysqlite cannot determine any types, yet. So, the only field of
cursor.description that pysqlite fills is name. All other fields are set
to None.
Another option would be to go with Another Python SQLite Wrapper
http://www.rogerbinns.com/apsw.html
from Roger Binns, which is available for SQLite3.
adi
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
