Re: [SQLObject] Bad side-effect when using sqlhub.doInTransaction()

2007-03-30 Thread Markus Gritsch
On 3/30/07, Oleg Broytmann <[EMAIL PROTECTED]> wrote: > Hello! > > On Wed, Mar 28, 2007 at 09:38:20PM +0200, Markus Gritsch wrote: > > the problem is, that > > doInTransaction() restores the old connection unconditionally to > > sqlhub.threadConnection, although self.getConnection() returns > > sql

Re: [SQLObject] Bad side-effect when using sqlhub.doInTransaction()

2007-03-30 Thread Markus Gritsch
On 3/30/07, Oleg Broytmann <[EMAIL PROTECTED]> wrote: > Hello! > > On Wed, Mar 28, 2007 at 09:38:20PM +0200, Markus Gritsch wrote: > > the problem is, that > > doInTransaction() restores the old connection unconditionally to > > sqlhub.threadConnection, although self.getConnection() returns > > sql

Re: [SQLObject] Bad side-effect when using sqlhub.doInTransaction()

2007-03-30 Thread Oleg Broytmann
Hello! On Wed, Mar 28, 2007 at 09:38:20PM +0200, Markus Gritsch wrote: > the problem is, that > doInTransaction() restores the old connection unconditionally to > sqlhub.threadConnection, although self.getConnection() returns > sqlhub.processConnection in case it is set. And since > doInTransacti

[SQLObject] Bad side-effect when using sqlhub.doInTransaction()

2007-03-28 Thread Markus Gritsch
Hi, the example below demonstrates a bad side-effect of sqlhub.doInTransaction(). I suppose the problem is, that doInTransaction() restores the old connection unconditionally to sqlhub.threadConnection, although self.getConnection() returns sqlhub.processConnection in case it is set. And since d