Sorry to bother you guys: is there any suitable workaround for this? I
tried the suggested one, but it does not work.
Regards
Marco
--
Marco Bizzarri
http://notenotturne.blogspot.com/
http://iliveinpisa.blogspot.com/
___
Zope maillist - Zope@zope.or
On Sat, Sep 20, 2008 at 8:24 AM, Dieter Maurer <[EMAIL PROTECTED]> wrote:
> Tres Seaver wrote at 2008-9-19 09:33 -0400:
>> ...
>>There is a special 'STICKY' state which prevents ghostifying, but it
>>can't be set from Python code. You could, however, set '_p_changed' on
>>the connection at the beg
Tres Seaver wrote at 2008-9-19 10:15 -0400:
> ...
>There are two problems here:
>
> - We need a way to keep the Pdata objects from evicting "precious"
> objects; ideally, Pdata instances would never be added to the cache
> at all. I worked a bit on a spike in which the Pdata iterator part
>
Tres Seaver wrote at 2008-9-19 09:33 -0400:
> ...
>There is a special 'STICKY' state which prevents ghostifying, but it
>can't be set from Python code. You could, however, set '_p_changed' on
>the connection at the beginning of the method, and then delete it at the
>end: changed objects can't be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Bizzarri wrote:
> Thanks for the suggestion, Tres, I'm trying it right now.
> I think this could be responsible for the problem I had a few months
> ago, under the name: "Asking advice on a Zope "stuck" (or: what did I
> do wrong?)"
> Do you t
On Fri, Sep 19, 2008 at 3:33 PM, Tres Seaver <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Marco Bizzarri wrote:
>> On Fri, Sep 19, 2008 at 9:23 AM, Marco Bizzarri
>> <[EMAIL PROTECTED]> wrote:
>>> Hi all.
>>>
>>> I'm working on an application which uses Zope (2.8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marco Bizzarri wrote:
> On Fri, Sep 19, 2008 at 9:23 AM, Marco Bizzarri
> <[EMAIL PROTECTED]> wrote:
>> Hi all.
>>
>> I'm working on an application which uses Zope (2.8, at the moment) and
>> ZPsycopgDA (toghter with a number of other products).
>>
>>