Could you explain the problems that should be solved by this a little? I find it rather hard to contribute anything useful without knowing some concrete examples ... Btw, i have a prototype Catalog that speeds up things a bit in usual scenarios. It is cacheable, implements an extended query interface and solves two performance issues with certain queries. I intend to put that into a proposal :-), but probably not until next week. If anybody wants to discuss that and/or take a look, just mail me. Wolfram ----- Original Message ----- From: "Chris Withers" <chrisw@nipltd.com> To: "Casey Duncan" <casey_duncan@yahoo.com> Cc: "Matt Hamilton" <matth@netsight.co.uk>; "Casey Duncan" <c.duncan@nlada.org>; "Steve Alexander" <steve@cat-box.net>; "Wolfram Kerber" <wk@gallileus.de>; <zope-dev@zope.org> Sent: Tuesday, December 04, 2001 10:36 PM Subject: Re: [Zope-dev] Searching/Indexing/ZODB/SQL/BerkleyDB
Casey Duncan wrote:
I think my first real proposal of any significance will be to replace the catalog with a truely industrial strength indexing bohemoth, that can be plugged into this whole "component arch." thingamawhammy.
*cough* --->
http://sourceforge.net/projects/pythonindexer
Care to help? I'm hoping to get started on it this evening with Docs and the like :-)
cheers,
Chris