On 11/30/05, Jeff Watkins <[EMAIL PROTECTED]> wrote: > > > This implicit behaviour will happen before Identity gets a hold of > > anything, right? I'm not quite sure how it works, but our code ends up > > checking turbogears.identity.current.user quite a bit and if > > turbogears.identity.current.user was selected outside of the current > > transaction then 'turbogears.identity.current.user ==' won't match any User > > objects that are grabbed within that transaction. > > First, I completely agree that a new transaction should be created to > wrap ALL database activities during the request. > > Unfortunately, I'm not certain how we can start a transaction before the > Identity filter gets a crack at the request short of creating another > filter that creates the transaction before starting to handle the > request and rolls it back if it hasn't been committed by the time the > request ends.
I thought of a spot: AutoConnectHub. That's where all of your connections come from, so it can just ensure that you get a Transaction out. The error handling aspect needs to be elsewhere (expose, likely). Kevin
