Any opinion about this?

On 2007-08-30 15:48:53 +0200, Christian Zagrodnick <[EMAIL PROTECTED]> said:


the documentation in the reads:

After-commit hook

Sometimes, applications want to execute code after a transaction is
committed or aborted. [...] The callable will be called with a Boolean
value representing the status of the commit operation as first
argument (true if successfull or false iff aborted) [...]

And indeed in the commit() method it reads:

            self.status = Status.COMMITTED
            t, v, tb = self._saveAndGetCommitishError()
            raise t, v, tb
            if self._manager:
   s: s.afterCompletion(self))

But in the abort() method the hooks are not called.

Is this intentional? If yes, the documentation should be adjusted to reflect that the hooks are *only* called if there *is* a commit and it is *failing*.

If not the hooks should be called in abort (my favourite) :)


Christian Zagrodnick

gocept gmbh & co. kg  ·  forsterstrasse 29 · 06112 halle/saale · fon. +49 345 12298894 · fax. +49 345 12298891

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -

Reply via email to