Chris Withers schrieb:
Jim Fulton wrote:

It's a shame ZODB doesn't turn POSKeyErrors into proper Broken objects
as it does when the class can no longer be imported. The problem with
POSKeyErrors is that they prevent you accessing *any object that refers
to the broken object* not just the missing object itself. This means
that when objects *do* go missing, the data loss can be much much worse
than it needs to be.

What does everyone else think?

I think you are right and this should be treated as a bug.

Okay, so I count two issues:

- packing and multiple mounted storages
- POSKeyErrors resulting in failure to load referring object rather than creation of a broken referred object

Where would you like me to file these bug reports?

How about the bugtracker?

gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle (saale) - germany - [EMAIL PROTECTED] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -

Reply via email to