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 structure, that would > be better. > > - This encourages mistake 2 above. > > 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.
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. cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev