Opps,
The code I said would be attached...
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:zope3-dev-
> [EMAIL PROTECTED] On Behalf Of Shaun Cutts
> Sent: Friday, February 24, 2006 10:18 PM
> To: 'Chris Withers'; [EMAIL PROTECTED]; 'zope3-dev&#x
Chris,
> You need to get into the habbit of CC'ing in the list you're replying
> too...
Sorry -- I was thinking that, if this was not a problem w/ ZODB and
external objects, but I've missed something in implementation, maybe I
should have been communicating on Zope3-users instead. Now I don't kno
Shaun,
You need to get into the habbit of CC'ing in the list you're replying too...
[EMAIL PROTECTED] wrote:
The data is in Postgres, but I already have a python data
marshalling/demarshalling/business logic used by other processes, so I want to
use this interface with ZOPE as well.
Okay, a
Shaun Cutts wrote:
But maybe my I'm misinterpreting the calls to __setstate__? It seems
unnecessary to call __setstate__ at all, as we already know the copies
in memory are fresh.
It sounds like you've implemented both __getstate__ and __setstate__.
Why?
What's your base concern here, 'cos I
Chris,
> -Original Message-
> From: Chris Withers [mailto:[EMAIL PROTECTED]
> Shaun Cutts wrote:
> > When a container gets pickled to be put into zodb, what happens to
the
> > subtree?
>
> If the container has references to stuff that is contains, one of two
> things could happen:
>
> 1.
Shaun Cutts wrote:
When a container gets pickled to be put into zodb, what happens to the
subtree?
If the container has references to stuff that is contains, one of two
things could happen:
1. If the contents subclass persistent, then they will end up in their
own pickle in the zodb and wi
