Roché Compaan wrote:
On Sun, 2006-07-02 at 17:46 +0100, Chris Withers wrote:
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?

I've explored a SQLCatalog (all indexes are in SQL) implementation
developed for the ERP5 project a while back. Besides writing a hell of a
lot a SQL, the idea is promising.

if you didn't want to use sql, there is the zemantic route.

rdflib lets you interfaces a number of different backends(sql or not) and comes with a rich query api.



 | david "whit" morriss
 | contact ::

 "If you don't know where you are,
  you don't know anything at all"

  Dr. Edgar Spencer, Ph.D., 1995

 "I like to write code like
 other ppl like to tune their
 cars or 10kW hifi equipment..."

 Christian Heimes, 2004

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -

Reply via email to