Rooney, Mike (ext. 324) wrote at 2007-1-15 15:49 -0500:
> ...
>raise MultipleUndoErrors(failures.items())
>MultipleUndoErrors: Undo error 0x15e1: Undo error 0x15e1: _loadBack() failed
>
>The actual line in FileStorage.py in _txn_undo_write that is raising the
>exception is:
> p, prev, v,
>If Jim is not right (and "DemoStorage" does not support "undo"),
>then it would not be difficult to derive a "RamFileStorage" from
>"FileStorage" that exactly works like "FileStorage" but have its
>file implemented as a "StringIO" (rather than a file on the file system).
Thanks for the clever sug
Rooney, Mike (ext. 324) wrote at 2007-1-10 17:01 -0500:
>Hi everyone, I have what I imagine is a pretty simple question. I am looking
>for a type of storage class (like FileStorage) which allows for undoing
>but stays in memory instead of on disk. If DemoStorage supported undo
>it would work but it
On Jan 10, 2007, at 5:01 PM, Rooney, Mike (ext. 324) wrote:
Hi everyone, I have what I imagine is a pretty simple question. I
am looking
for a type of storage class (like FileStorage) which allows for
undoing
but stays in memory instead of on disk. If DemoStorage supported undo
it would wor
