Dieter Maurer wrote:
You should be happy about the much more explicit information.
It may allow you to analyse your problem better.
This question has nothing to do with that problem, it just came up as a
result of once again being reminded that we use timestamps as
transaction ids.
For
Chris Withers wrote:
Dieter Maurer wrote:
You should be happy about the much more explicit information.
It may allow you to analyse your problem better.
This question has nothing to do with that problem, it just came up as a
result of once again being reminded that we use timestamps as
Dieter Maurer wrote:
A new proposal:
http://www.zope.org/Wikis/ZODB/MemorySizeLimitedCache
It outlines how to implement a ZODB cache limited not be the
number of containing objects but by their estimated memory size.
Feedback welcome -- either here or in the Wiki.
I'm going to reply here
Hi,
I have some random thoughts about ZODB Connection caching that I should have
written down a while ago... So I take this thread as an opportunity to do
so.
It would be interesting to have a solution for pure Read-Only Zope instances
(using a ZEO architecture, but it might work with a local
On Oct 5, 2006, at 9:37 AM, Jim Fulton wrote:
Russ Ferriday wrote:
Do you have some favorite documents that you would point me to as
most accurate or up to date?
No, because I haven't used ZODB documentation much myself. :)
Decent clues will be enough to get started.
- Doc in test or
Dmitry Vasiliev wrote:
Jim Fulton wrote:
When I originally developed the ZODB, I created a UML model:
http://www.zope.org/Documentation/Developer/Models/ZODB
This provided a fairly thorough and clear documentation of
the ZODB architecture at the time. It still contains useful information.
Dieter Maurer wrote:
Chris Withers wrote at 2006-10-5 09:52 +0100:
...
I'm wondering why we take on those issues rather than just use an
incrementing integer sequence instead?
With integer keys, you would not be able to pack to something
like n days before -- as you do not have any time in
Jim Fulton wrote at 2006-10-5 08:46 -0400:
...
I'll note that, as a guiding principle, any refactoring we do
should allow pure-python implementation. This means that APIs
need to be Python APIs, although we should consider efficient
C implementations when designing these APIs.
I
Jim Fulton wrote at 2006-10-5 13:58 -0400:
...
With integer keys, you would not be able to pack to something
like n days before -- as you do not have any time in your
storage file
You would still need to track times, but you could manage
this as transaction meta data, rather than using it
...
[Chris Withers]
Yes, but using timestamps also means:
- we're dependent on the system clock being accurate for no good reason
[Jim Fulton]
I'm hoping that Jeremy or Tim will chime in, since we considered switching
to integers a while back.
Not much to say here. It's not true that
10 matches
Mail list logo
