Roger Binns wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11/22/2010 06:58 PM, Chris Wolf wrote: > >>> Hmm, if you mean apsw, >>> > > Yes, I did. (I'm the author of APSW if that wasn't clear.) > > >>> that's actually one of the things I wanted to >>> do: change the >>> Connection signature to accept an already open database connection as an >>> alternative to >>> always opening a database file. >>> > > It has been a ticket for a while: > > http://code.google.com/p/apsw/issues/detail?id=79 > > Going the other way - handing a sqlite3 pointer from APSW to other code is > easy and there is an existing function to do that although it will cause > problems if the other code directly closes the connection or does silly > multi-threading tricks. Please update the ticket if you have use cases that > wouldn't have a large probability of memory corruption or crashes. >
I updated the ticket and provided a patch to connection.c. > Also, making APSW be a loadable extension means a separate compilation since > all calls have to go via a function pointer table not directly to SQLite so > it can't simultaneously be a Python extension and a SQLite extension, > although I guess the pointer table could be faked. > If the extension code is linked with sqlite3.o then sqlite api calls from the extension are dispatched via sqlite3_api* but sqlite calls from apsw are direct. In any case it works for me. > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkzraOAACgkQmOOfHg372QQaDwCfYg/Zrst9SQNgxpmqrk/oe56o > xEMAoJ0CaVxUVgz76conZemoRZ6m8pOC > =INqG > -----END PGP SIGNATURE----- > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
