Hello Tim Peters,
Tuesday, November 8, 2005, 8:26:00 PM, you wrote:
TP> I'm not familiar with "broken objects" in newer ZODBs, and didn't find any
TP> docs apart from the docstrings in broken.py. Brief overviews of new
TP> features often appear in NEWS.txt, but the news for ZODB 3.3a3 just says
[Dieter Maurer]
>>> You should file a bug report: "http://www.zope.org/Collectors/Zope";,
>>> category "database". This way, Tim can fix the hole in the
>>> "ConnectionStateError" check.
[Jim Fulton]
>> It's a mistake to rely on Tim alone to fix bugs.
[Dieter]
> Maybe, it is a mistake but most ZO
Jim Fulton wrote at 2005-11-6 11:22 -0500:
>Dieter Maurer wrote:
>>
>> You should file a bug report: "http://www.zope.org/Collectors/Zope";,
>> category "database". This way, Tim can fix the hole in the
>> "ConnectionStateError" check.
>
>It's a mistake to rely on Tim alone to fix bugs.
Maybe, it
Syver Enstad wrote at 2005-11-7 11:51 +0100:
>In ZODB 3.2 I can replace the _classFactory method on DB and locate the
>renamed/moved class by other means (a lookup table that maps old module
>classname pairs to another class in another module). If I change
>attributes of the persistent instance it
[Syver Enstad]
> In ZODB 3.2 I can replace the _classFactory method on DB and locate the
> renamed/moved class by other means (a lookup table that maps old module
> classname pairs to another class in another module). If I change
> attributes of the persistent instance it will be saved with the new
