Although I'm not an expert on _p_independent, AFAIK, it can only be used for
objects which are not in any way dependant on the state of other persistent
objects.
This is certainly not the case for BTrees, which is pretty much covers the
"data structures used for cataloguing and indexing".
I would definitely recommend discussing this on zodb-dev before going forward
with this. The current BTree intelligensia are over there.
-Casey
On Thursday 13 March 2003 04:39 pm, Dieter Maurer wrote:
> I am working on a CMS on top of ZODB for large amounts of
> large SGML/XML documents.
>
> To speed things up, a colleague started two import processes
> and we get incredible amounts of "database read conflict error"s
> from cataloguing (although we already use "QueueCatalog" for
> most indexes).
>
> I think, the data structures used for cataloguing and indexing
> could have a "def _p_independent(self): return 1".
>
> Does anybody objects?
>
> If not, I will implement "_p_independent" BTrees and friends.
>
>
> Dieter
>
> ___
> Zope-Dev maillist - [EMAIL PROTECTED]
> http://mail.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-announce
> http://mail.zope.org/mailman/listinfo/zope )
>
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
