This ZopeProduct provides a folder like object that stores its contents in a BTree. This means that many thousands of objects can be stored in such a folder without significant performance impacts. Also, the ZMI (Zope Management Interface) folder contents interface is more efficient.
BTreeFolder2 stores both data (the objects) and structure (meta_type to id mapping) in OOBTrees? which makes it significantly faster when dealing with lots of objects.
Note: Due the usage of BTrees? as storage for the objects BTreeFolders? are ordered, but only by id, which prevents them from behaving like OrderedObjectManagers?. Too much detail for mixed-audience page ?
The BTreeFolder2 product also includes a class that works with CMF and Plone.
- APIDocs:BTreeFolder2.html
- API docs
See also the programming docs on BTree.
BTreeFolder2 is used by CPS for its documents repository.
what are the down sides to using bTreeFolder2 -- Mon, 10 May 2004 15:03:47 -0700 reply
NEWBIE question: I understand in theory that you would use a bTreeFolder2 when you had the potential for a large number of items in a folder, but what are the disadvantages to using it? What problems exist with this as opposed to a Folder object?
what are the down sides to using bTreeFolder2 --simon, Thu, 18 Nov 2004 14:14:06 -0800 reply
None really that I know of, except that the folder listing in the ZMI (Zope Management Interface) is slightly less convenient - two clicks to edit instead of one, no object icons, etc.