On Wed, May 12, 2010 at 7:07 AM, Jim Fulton j...@zope.com wrote:
B. Change ZODB so that the root object is a variant of persistent
mapping that either refuses to store more than a small number of
objects, or at least issues a warning when more than a small
number of objects is stored.
A
On Wed, May 12, 2010 at 7:16 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/12/10 13:07 , Jim Fulton wrote:
B. Change ZODB so that the root object is a variant of persistent
mapping that either refuses to store more than a small number of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/12/10 13:21 , Jim Fulton wrote:
On Wed, May 12, 2010 at 7:16 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/12/10 13:07 , Jim Fulton wrote:
B. Change ZODB so that the root object is a variant
On Wed, May 12, 2010 at 7:23 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/12/10 13:21 , Jim Fulton wrote:
On Wed, May 12, 2010 at 7:16 AM, Jens Vagelpohl j...@dataflake.org wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/12/10
Jim Fulton wrote:
A. Change ZODB so that new databases have BTrees as root objects.
This has the advantage that BTrees are scalable. It has a number
of down sides:
- BTrees should only be used when keys are known to have a stable
ordering. If we had a scalable hash data
On Wed, 2010-05-12 at 20:16 +0100, Chris Withers wrote:
Jim Fulton wrote:
C. I'd really like to be able to configure what the root object is as
database creation time. That way it can be application specific.
That sounds reasonable, but doesn't address the default behavior.
Default