On Sunday 17 February 2008, Oleg Broytmann wrote: > On Sun, Feb 17, 2008 at 12:20:54AM +0200, Dan Pascu wrote: > > If I'm for a change, then I'm for removing this limitation from > > sqlite as well rather than putting it in other backends too. > > Thank you for stepping in. > > As for SQLite - the limitation is (at least was) imposed by the > SQLite backend, not PySQLite, even less SQLObject: > > http://sqlite.org/faq.html#q6 : > > "sqlite3 structure could only be used in the same thread that called > sqlite3_open() to create it. You could not open a database in one > thread then pass the handle off to another thread for it to use." > > Oleg.
I know. That is more of a wishlist item I have, but I know the limitation comes from the sqlite python module and cannot be fixed in sqlobject. However with mysql this is not imposed by python-mysqldb. With mysql I routinely use connections from the pool in multiple threads without issues, as well as create the connections in the main thread at startup and use them later from dedicated threads (also without issues). -- Dan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ sqlobject-discuss mailing list sqlobject-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
