[ Tim Peters wrote:]
[Jürgen Herrmann]
...
so, what i need is a way to have my mechanism called before transaction
commits (would be possible to use the hooks provided by zodb 3.4 for
that, sure) and cycle through all modified objects (that's where the
hooks in 3.4 are not enough for me,
[Jürgen Herrmann]
hmm, as it seemed quite impossible the way i wanted it, i almost dropped
it from my wishlist. now you say, it's doable...
It would be possible to add new official APIs to ZODB to supply some notion
of the collection of all modified objects, at the level ZODB sees objects.
Of
[ Tim Peters wrote:]
[Jürgen Herrmann]
hmm, as it seemed quite impossible the way i wanted it, i almost dropped
it from my wishlist. now you say, it's doable...
It would be possible to add new official APIs to ZODB to supply some
notion
of the collection of all modified objects, at the
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
hi all!
i'm trying to form a patch that will result in a method
_before_commit()
being called on each modified object in a transaction (if that method
exists of course) right before commit.
main sense is to automate/delay
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
hi all!
i'm trying to form a patch that will result in a method
_before_commit()
being called on each modified object in a transaction (if that method
exists of course) right before commit.
main sense is
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
hi all!
i'm trying to form a patch that will result in a method
_before_commit()
being called on each modified object in a transaction (if that method
exists of course) right
[Jürgen Herrmann]
...
so, what i need is a way to have my mechanism called before transaction
commits (would be possible to use the hooks provided by zodb 3.4 for
that, sure) and cycle through all modified objects (that's where the
hooks in 3.4 are not enough for me, they don't provide any way
