Hanno Schlichting wrote:
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
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
Chris Withers wrote:
Hanno Schlichting wrote:
Nope. DateTime objects are plain old-style classes and don't inherit
from persistent.*.
Hmm, oh well, my bad...
In that case it must just be that their pickled form is huge compared to
an int ;-)
Sure:
len(cPickle.dumps(DateTime.DateTime(),
On Wed, May 27, 2009 at 12:17:36PM +0200, Hanno Schlichting wrote:
Chris Withers wrote:
Hanno Schlichting wrote:
They are incredibly expensive to unpickle since all
the DWIM magic in their __init__ get called each time, though.
How come? Unpickling doesn't call __init__ and I don't see
Marius Gedminas wrote:
On Wed, May 27, 2009 at 12:17:36PM +0200, Hanno Schlichting wrote:
Chris Withers wrote:
Hanno Schlichting wrote:
They are incredibly expensive to unpickle since all
the DWIM magic in their __init__ get called each time, though.
How come? Unpickling doesn't call
On Wed, May 27, 2009 at 03:35:26PM +0200, Hanno Schlichting wrote:
Marius Gedminas wrote:
On Wed, May 27, 2009 at 12:17:36PM +0200, Hanno Schlichting wrote:
Chris Withers wrote:
Hanno Schlichting wrote:
They are incredibly expensive to unpickle since all
the DWIM magic in their __init__
