Jens Vagelpohl wrote:
On 21 Mar 2007, at 17:29, Chris Withers wrote:
I'm hoping for some means to just lop transactions off the end of the
Data.fs until I get to the point in time I want...
Why don't you just record the exact size of your Data.fs before starting
your migration and then trunca
Dennis Allison wrote:
The ZODB is an append only file system so truncating works just fine.
Yup, but it's finding the location to truncate back to that's the
interesting bit.
And that I'm lazy and really want to be able to do:
python rollback.py 2007-03-21 09:00
You can use any
of the sta
Jeremy Hylton wrote:
The MVCC implementation might not be prepared to cope with an explicit
call to invalidate.
oops?
Yould also achieve this by calling some method on
the object, right? _p_invalidate()? I don't remember the details.
Well, we're not doing any explicit invalidation like tha
Chris Withers wrote:
I'm writing/running a bunch on migration processes on a 30GB
Data.fs, I'm hoping it's easier to roll back the Data.fs to before I
started my migration run than it is to grab a new copy on the ZODB from
somewhere...
Demostorage, perhaps?
--
Benji York
Senior Software Engin
I did use the deadlockdebugger. There were three threads doing folder listing
and the last one was in the wait method doing a continuous loop listening for
the server.
The server was disconnected. Somehow the client just never knew.
-Original Message-
From: Christian Theune [mailto:[E
Benji York wrote:
Chris Withers wrote:
I'm writing/running a bunch on migration processes on a 30GB Data.fs,
I'm hoping it's easier to roll back the Data.fs to before I started my
migration run than it is to grab a new copy on the ZODB from somewhere...
Demostorage, perhaps?
Nah, the change
Chris Withers wrote:
Benji York wrote:
Chris Withers wrote:
I'm writing/running a bunch on migration processes on a 30GB Data.fs,
I'm hoping it's easier to roll back the Data.fs to before I started my
migration run than it is to grab a new copy on the ZODB from somewhere...
Demostorage, perha
Benji York wrote:
Nah, the changes need to be permenant, tested, and then rolled back...
I can't reconcile "permanent"
ie: committed to disk, not DemoStorage...
and "rolled back". :)
undo the changes committed to disk, to a point in time, once the results
have been tested.
If the app n
Am Donnerstag, den 22.03.2007, 15:00 + schrieb Chris Withers:
> Benji York wrote:
> >> Nah, the changes need to be permenant, tested, and then rolled back...
> >
> > I can't reconcile "permanent"
>
> ie: committed to disk, not DemoStorage...
>
> > and "rolled back". :)
>
> undo the changes
Chris Withers wrote at 2007-3-22 08:43 +:
>Dennis Allison wrote:
>And that I'm lazy and really want to be able to do:
>
>python rollback.py 2007-03-21 09:00
You have been told that you can specify a "stop" time
and the storage will "stop" at the given time.
Thus, you look at the code how this
10 matches
Mail list logo
