Re: [SQLObject] Hung transactions on object creation

[Sidnei da S. <si...@aw...>]

On Mon, Oct 27, 2003 at 02:59:40PM -0600, Ian Bicking wrote:
| So for some reason an exception propagated out of SQLObject.new won't 
| cause the TransactionManager to roll back the transaction, even though 
| exceptions anywhere else do work.  How odd.  What does SQLObject's 
| connection to TransactionManager look like?
| 
| Does it work any differently if you successfully create (or interact 
| with) a SQLObject instance, then get an exception in SQLObject.new?  
| (As opposed to an exception in SQLObject.new being the first query for 
| the transaction)

Ok, I seem to have located the source of problem here. The problem
showed to be that I didn't read the traceback correctly :) The
exception was actually happening during TestCase.setUp(), so there was
no-one to catch the exception and call Transaction.abort(). In normal
Zope operation, ZPublisher does this job, that's why I missed
it. Sorry for the inconvenience. It was a SNAFU [1].

[1] http://www.dict.org/bin/Dict?Query=snafu&Form=Dict1&Strategy=*&Database=vera

[]'s
-- 
Sidnei da Silva <si...@aw...>
dreamcatching :: making your dreams come true
http://awkly.org

A year spent in artificial intelligence is enough to make one believe in God.