.
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) :)
Regards,
--
Julien Anguenot | Nuxeo RD (Paris, France)
Open Source ECM
the amount of entries in the changelog
for this 3.7 branch...
For the original topic (i.e : the ZODB blobs), we didn't found the time
to play with it, until now, at Nuxeo to give any feedbacks.
Cheers,
J.
--
Julien Anguenot | Nuxeo RD (Paris, France)
Open Source ECM - www.nuxeo.com
CPS
comes around.
I think you should push it further and integrate it in a branch of off
the ZODB trunk as a first step. I'm willing to help out on this.
A persistent queue is something more than necessary on large scale
production instances...
J.
--
Julien Anguenot | Nuxeo RD (Paris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Branch merged in rev [41164].
Cheers,
J.
Julien Anguenot wrote:
Hi there,
I did a an implementation, along with tests, of the after commit hooks
support on the ZODB transaction. For those who didn't follow the
previous thread
://svn.nuxeo.org/trac/pub/file/CPSCore/trunk/commithooks.py
Now, in the meanwhile, if someone has time for a review of the branch
he's welcome.
Cheers,
J.
Julien Anguenot wrote:
Hi there,
I did a an implementation, along with tests, of the after commit hooks
support on the ZODB
that could be done on
another node of your cluster)
There's a remaining XXX within _callAfterCommitHooks() that would
certainly appreciate a review ;)
Cheers,
J.
- --
Julien Anguenot | Nuxeo RD (Paris, France)
CPS Platform : http://www.cps-project.org
Zope3 / ECM : http://www.z3lab.org
mail
this within the
README.txt of ZODB.
To test the build, first build the externals and add the src dir to
your PYTHONPATH,
% python setup.py build_ext -i
% export PYTHONPATH=`pwd`/src:$PYTHONPATH
Then run the test script::
% python test.py
Cheers,
J.
- --
Julien Anguenot
.
J.
- --
Julien Anguenot | Nuxeo RD (Paris, France)
CPS Platform : http://www.cps-project.org
Zope3 / ECM : http://www.z3lab.org
mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http
before and after
commit hook system ?
J.
- --
Julien Anguenot | Nuxeo RD (Paris, France)
CPS Platform : http://www.cps-project.org
Zope3 / ECM : http://www.z3lab.org
mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Julien Anguenot wrote:
I'm gonna respond to a number of emails at once. :)
Tim Peters wrote:
[Tim]
...
Julien provided links to code that already uses the new feature:
As an Indexation Manager :
http://svn.nuxeo.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Julien Anguenot wrote:
[...]
I would like to order the before commit hooks on a transaction by being
able to specify an order for a subscriber at registration time. For the
moment, they are called in the order they've been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Peters wrote:
[Julien Anguenot]
...
To make it clear the idea is if you got this and if we call it order.
Callback Ca order 0
Callback Cb order 99
Callback Cc order -99
The order of execution will be Cc Ca and then Cb.
Note the ones
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I created a branch there :
http://svn.zope.org/ZODB/branches/anguenot-ordering-beforecommitsubscribers/
See changeset 37789
Check the changeset log for more information about the implementation.
J.
Julien Anguenot wrote:
Hi,
I
with a default value to 0 added
to the registration method.
We could just insert the subscriber wihin the queue according to this
order parameter if found *or* sorting the queue according to this
parameter before flushing the queue and calling the hooks.
What do you think ?
J.
- --
Julien
14 matches
Mail list logo
