[Eric Brun, with a corruption problem]
This is a good place to discuss it, but I can't tell you more here than I
said on zope-dev earlier this morning:
http://mail.zope.org/pipermail/zope-dev/2005-June/024941.html
...
I have tried to do a fsrecover, it removes a transaction.
...
fstest say
[Kevin Dangoor]
I'm working with the ZODB 3.4 beta, and I'm working on getting Catalog
running with it. I noticed that the _Persistence module is not being
built. Is this because ExtensionClass is not included and _Persistence
requires ExtensionClass?
Catalog has a couple of acquisition
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of the objects in the cache.
I therefore propose the implementation of
Dieter Maurer wrote:
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of the objects in the cache.
I therefore
Shane Hathaway wrote:
Dieter Maurer wrote:
Currently, the ZODB cache can only be controlled via the maximal number
of objects. This makes configuration complex as the actual limiting
factor is the amount of available RAM and it is very difficult to
estimate the size of the objects in the
[Tim Peters]
...
Hmm. _Persistence.c should be removed from ZODB. Zope 2.8 has its own
copy now, in its lib/python/Persistence/ directory.
Sorry, I lied about that part. Zope 2.8 copies its Persistence directory
from ZODB, so _Persistence.c can't be removed from ZODB yet. Grr --
which
On 6/2/05, Tim Peters [EMAIL PROTECTED] wrote:
[Kevin Dangoor]
I'm working with the ZODB 3.4 beta, and I'm working on getting Catalog
running with it. I noticed that the _Persistence module is not being
built. Is this because ExtensionClass is not included and _Persistence
requires
