-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote: > Raphael Ritz wrote: > >> Since you ask so explicitly ;-) >> >> I agree with Florent: Your site's _USERES_ should never get >> an error thrown at. > > > Even if they're potentially destroying their own data as a result?!
Chris, you can't seem to get the point the fact that the damage, if any, is *already done*, in some previous request. The log messages we are talking about here are a result of the code *noting* the already-created inconsistency. The proof of the pudding here is that this issue does *not* result in "data loss" for users: the symptom can be resolved by reindexing the entire catalog, for instance (the inconsistent data is secondary, not primary). Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCoHL5+gerLs4ltQ4RAjWvAKC5+SOU4DRUoX/ollOE6yC++TelFQCgw4iS a4xpiqoo7utrb1JCrqpfTLk= =29f6 -----END PGP SIGNATURE----- _______________________________________________ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests