On Tue, Jan 26, 2010 at 12:26:51PM +0100, Sophana K wrote:
> Do you have an idea what could explain the different tracebacks I got?
> Could it be related to multithreading?
They could be related to multithreading; actually, I am almost
completely sure they are related. On the other hand they could be related
to a "wrong" sequence of calls (attribute access) - a code accessed an
attribute of the connection, the access gets redirected to the transaction,
but 'self' is wrong and there are problems with further attribute access;
similar to a bug I fixed by adding .close() method to Transaction class
because without it .close gets redirected to DBConnection.close but that's
wrong for a transaction.
Oleg.
--
Oleg Broytman http://phd.pp.ru/ p...@phd.pp.ru
Programmers don't die, they just GOSUB without RETURN.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
sqlobject-discuss mailing list
sqlobject-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
