[ZODB-Dev] Preventing a folder from being packed

[sean.upton at uniontrib.com]

Forgive my ignorance, but wouldn't this be a bit of work?  Since ZODB
essentially just persists objects and references, I wonder how much of a
mismatch and additional complexity the Zope-level notion of
folders/containment hierarchies would add to the storage.  How smart should
the storage be?  I like the per-class adjustment of history, because this
maps well in and out of Zope, but wouldn't notions of containment be harder
to preserve?  

My thinking is that this is what DBTab is likely the solution for: mount a
different storage for every containment hierarchy in Zope that needs
specific performance, feature, and pack capability sets?  Would this not be
a more simple solution?

Sean

-----Original Message-----
From: Toby Dickenson [mailto:tdickenson at geminidataloggers.com]
Sent: Thursday, May 15, 2003 9:25 AM
To: Jeremy Hylton; Dennis Heltzel
Cc: zodb-dev at zope.org
Subject: Re: [ZODB-Dev] Preventing a folder from being packed


On Thursday 15 May 2003 4:33 pm, Jeremy Hylton wrote:
> On Thu, 2003-05-15 at 11:03, Dennis Heltzel wrote:
> > There are certain folders where I want to keep all undo forever. Is
> > there any way to protect the folder so that packing the ZODB will not
> > remove the undo for objects in that folder ?

DirectoryStorage can keep extra history for instances of specified classes, 
but not a folder.

http://dirstorage.sourceforge.net/keepclass.html

It might not be hard to add, if you want to beta test the feature?

-- 
Toby Dickenson
http://www.geminidataloggers.com/people/tdickenson

_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev at zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev