[ZODB-Dev] ZODB _v_ attributes are tricky

[Dieter Maurer]

Toby Dickenson wrote at 2004-4-2 11:06 +0100:
>On Friday 02 April 2004 02:13, Shane Hathaway wrote:
>
>> ZODB destroys volatile attributes only when
>> unloading objects.  ZODB unloads objects after another connection
>> changes them.  Also, the ZODB garbage collector unloads objects at the
>> end of transactions.
>
>The garbage collector can also be triggered explicitly by application code, 
>and future improvements to the garbage collector might unload objects at 
>other times too. In short, you should assume that _v_ variables might 
>disappear at any time.

You still remember that I posted a patch to "zodb-dev" which allows
to prevent invalidation outside main transaction boundaries.

I still hope, that functionality like that will enter the
official ZODB code. It is essential for "_v_" attribute use.

-- 
Dieter