On Oct 17, 12:18 pm, Roger Binns <rog...@rogerbinns.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Dennis Lee Bieber wrote: > > I suspect, besides building an sqlite3.dll (if Windows), you might > > have to modify the pysqlite DB-API adapter to support whatever new > > arguments have been added to various calls (most like the db.connect() > > parameters have changed to require an encryption password) > > The extension requires an extra C api call after the database is opened to > set the encryption key. (There is also another API to change the key.) > > This means that it is not possible for the same pysqlite to work against > SQLite built with and without the encryption extension. The changes needed > in pysqlite are a simple matter of programming although you'll want them > incorporated back into the core so you don't have to maintain them (wrapped > in some sort of ifdef). > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org > > iEYEARECAAYFAkrZb6sACgkQmOOfHg372QRSYwCg2J/YSvkqLs8EJ1iJkE2wnbaY > nl0AoKYxgMEnBQNjDyYHv1xWC0Tia74U > =eA2B > -----END PGP SIGNATURE-----
One problem is that pysqlite is written in C, and I have no knowledge of C whatsoever. I will try to incorporate the changes mentioned, but I am not sure now at all :-( K -- http://mail.python.org/mailman/listinfo/python-list
