Patrick Gerken wrote at 2006-9-22 10:17 +0200:
> ...
>Even the first checkin of the filestorage makes a
>self.read_index(...start = start...)
>which updates the index from the oldest tid known to the index.
>I can only imagine that the index gets invalidated if the
>self._check_sanity() returns 0 t
Wolfgang Schnerring wrote:
> Hi,
>
> I'm working with Theuni on the BlobStorage, and am trying to understand the
> different 2-Phase-Commit protocols that are in use in ZODB at the same time.
> As I understand it, tpc_* is the old protocol, and prepare/commit is the new
> protocol.
>
> The sequ
Hi,
I'm working with Theuni on the BlobStorage, and am trying to understand the
different 2-Phase-Commit protocols that are in use in ZODB at the same time.
As I understand it, tpc_* is the old protocol, and prepare/commit is the new
protocol.
The sequence in Transaction._commitResources is
tpc
On Sep 22, 2006, at 2:48 AM, Christian Theune wrote:
...
One of the last things I remember is that indexes can not be rebuilt
partially but are rebuilt completely.
If the existing index is valid, then only new data are read if it
isn't current.
I think this is what Patrick was referring to
On 9/22/06, Christian Theune <[EMAIL PROTECTED]> wrote:
Hi,
Patrick Gerken wrote:
> Hello,
>
> its funny, like Garth in may this year I am looking into making a HA
> system with ZEO for an ERP5 deployment. In my case I don't need to
> care for data replication, all is stored on a SAN considered
