RE: [ZODB-Dev] before commit hook

[Tim Peters, on adding getBeforeCommitHooks()] >> Note that Zope 2.8b1 was already released (yesterday) with a ZODB 3.4 >> alpha, so strictly speaking no new features should be added to ZODB 3.4. >> But if you can slam code and tests for this in quickly, I'll look the >> other way (I think adding a

Re: [ZODB-Dev] before commit hook

Tim Peters wrote: > def getBeforeCommitHooks(self): > > Note that Zope 2.8b1 was already released (yesterday) with a ZODB 3.4 alpha, > so strictly speaking no new features should be added to ZODB 3.4. But if > you can slam code and tests for this in quickly, I'll look the other way (I > think add

RE: [ZODB-Dev] before commit hook

[Florent Guillaume] > FYI in CPS we use a simple backport of the before commit hook to ZODB > 3.2: > > > For now we use it to delay indexing of some objects to the end of the > transaction (to avoid

[ZODB-Dev] before commit hook

FYI in CPS we use a simple backport of the before commit hook to ZODB 3.2: http://cvs.nuxeo.org/cgi-bin/viewcvs.cgi/CPS3/CPSCompat/PatchZODBTransaction.py?rev=1&view=markup For now we use it to delay indexing of some objects to the end of the transaction (to avoid indexing twice the same object fo