Sean Allen wrote:
been looking for anything along those lines.

in particular, strategies and gotchas for how to store objects.
everything i've found is basically just a single type of object being stored.

i'm really interested in tutorials and information on the best ways to setup
large complicated hierarchies and all the various gotchas etc.

anything like that exist?

A good jumping off point is the wiki:

The beauty of using the ZODB is that it really makes no difference whether you are storing homogeneous or heterogeneous hierarchies of objects.

If you are likely to have a large number of objects in any one folder then make sure it is BTree based. This is a scalable data structure, so the whole list does not have to be loaded into memory to access a single child object.

It also pays to keep your zodb content objects simple. Adding behaviour through the component architecture is much more flexible in the long run (which is not to say you need to use the Zope CA to use the ZODB).

Hope that helps


For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -

Reply via email to