Chris Withers wrote at 2006-7-2 17:46 +0100:
>Yes, indexing seems to be the big problem here...
>I wonder if there's a way to move indexing out of "the zodb".
>The main things I get from ZODB are simplicity of data storage (ie: just
>playing with python objects) and robustness of data.
>For the first point, indexing is never simple ;-)
>For the second, if indexes become corrupt, they can be rebuilt.
>I wonder if there's something to be said for having a generic object
>indexing service that didn't use ZODB but used its own local indexes and
>re-indexed as needed or if the indexes are corrupt?
It would at least need to be transaction aware (otherwise,
you risk index inconsistencies as soon as transactions are aborted)
and it would need to be server based (such that multiple clients
can index and search concurrently).
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org