There's been at least a couple of threads about automatically doing transactions at the request boundaries in some form. The idea will probably be something along the lines of having your methods wrapped in a transaction unless you tell expose not to do so.
This will easily handle rolling back if an exception occurs within the code. There's a good chance this will arrive in 0.9. Kevin On 11/5/05, DaveS <[EMAIL PROTECTED]> wrote: > > I'm trying to figure out how to structure my code so transactions do > the right thing when exceptions are raised. So far I've got > > def update(self): > hub.begin() > self.modify_database() > if i_dont_like_things: > hub.rollback() > else: > hub.commit() > hub.end()
