On 12/1/05, Chris Withers <[EMAIL PROTECTED]> wrote:
> Ah, okay, so having DateTime sublcass Persistent would only really
> matter if a had _lots_ of DateTime attributes. Does this ever happen?
Well, in a calendar each event has at least one. And you can have
quite many events. But on the other hand, if this ever became an
issue, it would (in any good architecture) be easy to substitute the
standard datetime for a
> > If the same DateTime object is referenced by many persistent objects, there
> > can be major storage efficiencies is making DateTime persistent, because the
> > "many other objects" can all point to the same pickle. I don't know, but I
> > doubt that's a likely scenario for DateTime objects.
> Indeed :-/ Oh well...
> Simplistix - Content Management, Zope & Python Consulting
> - http://www.simplistix.co.uk
> For more information about ZODB, see the ZODB Wiki:
> ZODB-Dev mailing list - ZODB-Dev@zope.org
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org