[ZODB-Dev] ZODB and ORBit-Python problems

[Greg Ward]

On 22 May 2001, Christian Robottom Reis said:
> I would tend to agree, but the problem remains of searching for objects in
> the storage by attribute values; AFAICS we still have to load and check;
> the QL associated with structured storage could make this much faster. But
> it's a performance issue, perhaps.

It sounds like you don't want a query language per se, but rather an
efficient query mechanism.  So would I!  I don't much mind writing
queries in Python -- simple queries are probably a bit wordier than they
would be with (say) OQL, but at least I don't have to learn another
language.  More importantly, I don't have to embed that new language in
my code -- I've never understood why people think embedding SQL into
another language is a good thing, and having an OQL-speaking object
database at my fingertips would be unlikely to change my opinion.

However, I *would* like to see some (documented and comprehensible)
infrastructure for indexing a ZODB.  (I've attempted to read the code
for Catalog and related classes, but came away understanding less than I
went in with.)  As it stands, if I want to query every Thing object in
our database, I have to loop over our collection of all Things, load
each into memory, and query it.  Our database isn't very big, so this
isn't a big deal (yet).  I can see that it would be a showstopper for
someone with (say) hundreds of thousands of Thing objects in their
database.

        Greg
-- 
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org