Re: [pysqlite] tracing

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Edzard Pasma wrote:
> Having the cursor method available as a class is not an issue if this appears difficult. One can still make an adapter class around it.

The cursor only has two methods - execute and executemany so an adaptor
is no big deal.

> I have two usage cases, forgive me if it is all experimental use. First is a module apsw_dbapi2 that provides a Pysqlite/DBAPI2 compatible interface. 

Other than the connect/Connection thing they are compatible for trivial
queries, but beyond that are fundamentally different like all the extra
transaction stuff in pysqlite and all the extra SQLite stuff in APSW
(vfs, vtables, multiple statements etc).

> It is intended to check if application errors might be resolved through APSW instead of Pysqlita (especially for the locking mechanism).

What exactly do you mean by "application errors" and "locking mechanism"?

> Second is a pass-time project for a SQL-based chess engine. The performance is determined for 90 % in SQLite. To measure this, the Execution Trace option won't do. You need not only the start but also the end of each execute call.

http://apsw.googlecode.com/svn/publish/connection.html#apsw.Connection.setprofile

> This is indeed a perfect solution to leave the application unchanged. Possibly one may publish his mylogger.

I'll try to produce something during the next week.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkpRT4ACgkQmOOfHg372QTnJwCfWIxAERssBBMisvwzTpjySs82
jgIAninFfxBapIIcyRqy/Yla7fJvgK26
=4nP8
-----END PGP SIGNATURE-----