Hi All,
Is there any existing method or script for rolling back a ZODB
(filestorage-backed in this case, if that makes it easier) to a certain
point in time?
eg: Make this Data.fs as it was at 9am this morning
If not, I'll be writing one, where should I add it to when I'm done?
cheers,
Chr
On Mar 21, 2007, at 6:41 AM, Chris Withers wrote:
Hi All,
Is there any existing method or script for rolling back a ZODB
(filestorage-backed in this case,
Back end to what?
if that makes it easier) to a certain point in time?
Do you actually want to modify the file? Or do you simply w
[ Jim Fulton ]:
|Before we talk about adding it anywhere, I'd like to see the
|semantics defined more clearly.
I guess what Chris meant was:
Given a pivot point in time (date and time),
for *all* objects in the database (the whole Data.fs)
will suffer UNDO over transactions whose timestam
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> On Mar 21, 2007, at 6:41 AM, Chris Withers wrote:
>
>> Hi All,
>>
>> Is there any existing method or script for rolling back a ZODB
>> (filestorage-backed in this case,
>
> Back end to what?
>
>
>> if that makes it easier) to
On Mar 21, 2007, at 9:59 AM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
On Mar 21, 2007, at 6:41 AM, Chris Withers wrote:
Hi All,
Is there any existing method or script for rolling back a ZODB
(filestorage-backed in this case,
Back end to what?
Jim Fulton wrote:
I wasn't asking about implementation.
Here are some questions:
- Should this create a new FileStorage? Or should it modify the existing
FileStorage in place?
Probably create a new one (analogous to a pack). Seems safer than
truncating to me.
- Should this work while t
Jim Fulton wrote:
On Mar 21, 2007, at 6:41 AM, Chris Withers wrote:
Hi All,
Is there any existing method or script for rolling back a ZODB
(filestorage-backed in this case,
Back end to what?
I meant as opposed to BDBStorage or OracleStorage ;-)
I don't know whether to attempt this at the
Rodrigo Senra wrote:
I guess what Chris meant was:
Given a pivot point in time (date and time),
for *all* objects in the database (the whole Data.fs)
will suffer UNDO over transactions whose timestamp is
greater (more recent) than the given pivot timestamp.
Sounds about right...
Never
Tres Seaver wrote:
1. Open the existing file in time-travel mode (readonly, so that it
loads no transactions later than the given point). The 'stop'
parameter to the FileStorage initializer is the one which
triggers time-travel.
2. Open a new, writable filestorage.
3. Run
Jim Fulton wrote:
- Should this create a new FileStorage?
No.
Or should it modify the existing
FileStorage in place?
Yes.
- Should this work while the FileStorage is being used?
No.
- Should this behave transactional?
Not sure what you mean... in terms of being able to "undo the u
Laurence Rowe wrote:
- Should this create a new FileStorage? Or should it modify the
existing FileStorage in place?
Probably create a new one (analogous to a pack). Seems safer than
truncating to me.
Nah, this is working on a copy of production data, not the real thing.
Disk space is an iss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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 you
Chris,
The ZODB is an append only file system so truncating works just find. I
have used truncation occasionally to fix a coddled ZODB. You can use any
of the standard tools (fsrecover, for example) to find the transactions
and their dates. The position in the file is part of the fsrecover
out
Since we implemented this, any task that takes more than a few seconds (ie.
pack the database) throws a clientdisconnectederror. I am hoping someone out
there can shed some light on what might be happening.
-Original Message-
From: Christian Theune [mailto:[EMAIL PROTECTED]
Sent: Wed
Jim Fulton wrote at 2007-3-21 10:06 -0400:
> ...
>
>On Mar 21, 2007, at 9:59 AM, Tres Seaver wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Jim Fulton wrote:
>>> On Mar 21, 2007, at 6:41 AM, Chris Withers wrote:
>>>
Hi All,
Is there any existing method or script f
Hi,
I haven't had a look at your patch earlier.
With your error description and with the patch together, it makes sense
to me. You patched the "wait" method which is described as:
def wait(self, msgid):
"""Invoke asyncore mainloop and wait for reply."""
This method is used to wait fo
16 matches
Mail list logo
