Today I stumbled over an unexpected behavior of savepoints. As far as
I'm able to understand savepoints they mark a well defined state in the
middle of a transaction. A savepoint is invalid if its transaction is
committed or another savepoint is created. Well nesting savepoints would
be a nice
Christian Heimes wrote:
Today I stumbled over an unexpected behavior of savepoints. As far as
I'm able to understand savepoints they mark a well defined state in the
middle of a transaction. A savepoint is invalid if its transaction is
committed or another savepoint is created. Well nesting
Tim Peters wrote:
[Christian Heimes]
...
Something else strikes me. Why am I unable to roll back to the same
savepoint multiple times?
Because that's how it works wink. Maybe Jim can explain why quickly --
offhand I'm not sure. I don't think it could be guessed from the interface
docs:
[Christian Heimes]
...
From my point of view I can't see a reason why the ZODB forbids a
second rolback to the savepoint.
[Jim Fulton]
I agree. This should be changed.
Sounds good to me -- it looks easy, so I'll do it wink.
___
For more
Jim Fulton wrote:
From my point of view I can't see a reason why the ZODB forbids a
second rolback to the savepoint.
I agree. This should be changed.
Great!
HTH :)
Christian
___
For more information about ZODB, see the ZODB Wiki:
[Christian Heimes]
From my point of view I can't see a reason why the ZODB forbids a
second rolback to the savepoint.
[Jim Fulton]
I agree. This should be changed.
[Tim Peters]
Sounds good to me -- it looks easy, so I'll do it wink.
Something subtler than I've been able to figure out yet
[Tim Peters]
Something subtler than I've been able to figure out yet is going wrong,
so I made a tim-savepoint branch. All the tests pass, but ...
Br. The pickle cache invalidate method (which is coded in C, so isn't
visible from pdb) clears the dictionary passed to it, and when using a
[Tim Peters]
...
The good news is that, while it was hard to find, it's a one-line repair.
Alas, that wasn't the end of it either. I think I'm at the end now, and all
the tests are passing again (including new tests to provoke new problems I
found).
A savepoint (of the data manager Connection
Tim Peters wrote:
Today I stumbled over an unexpected behavior of savepoints. As far as I'm
able to understand savepoints they mark a well defined state in the
middle of a transaction.
A savepoint is invalid if its transaction is committed
or another savepoint is created.
No, that's not the
IIRC, the old implementation of savepoints kept a copy of the index at
the time the savepoint was taken so that you could rollback to it
multiple times. I don't think there's any way to avoid such a copy.
Jeremy
On 7/11/05, Tim Peters [EMAIL PROTECTED] wrote:
[Tim Peters]
...
The good news
10 matches
Mail list logo