2009/5/27 Chris Withers <ch...@simplistix.co.uk>:
> Laurence Rowe wrote:
>> Jim Fulton wrote:
>>> Well said. A feature I'd like to add is the ability to have persistent
>>>  objects that don't get their own database records, so that you can get  the
>>> benefit of having them track their changes without incuring the  expense of
>>> a separate database object.
>> +lots
>> Hanno Schlichting recently posted a nice graph showing the persistent
>> structure of a Plone Page object and it's 9 (!) sub-objects.
>> http://blog.hannosch.eu/2009/05/visualizing-persistent-structure-of.html
> That graph isn't quite correct ;-)
> workflow_history has DateTime objects in it, and I think they get their own
> pickle.
> I had a major win on one CMFWorkflow project by changing the workflow
> implementation to use a better data structure *and* store ints instead of
> DateTime object. CMF should change this...

Good point, though it is 'correct' for an object that has not
undergone any workflow transitions yet, as is the case here ;)

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  ZODB-Dev@zope.org

Reply via email to