Re: Built-in/standard/default catalog for ZODB?

 
> On Oct 28, 2017, at 8:15 PM, Jim Fulton <[email protected]> wrote:
> 
> I haven't kept up with the various implementations. Is there one (or a small number of) catalog implementation we should call out in documentation and presentations?  Any candidates (e.g. repoze.catalog) should be independent of other application frameworks.

I just went through the list of catalogs last week for my talk.  

Zope.catalog is all tied up with zope.interfaces    Way way too complex.  Reject. 

Without remembering the details. grok.catalog gets the model all wrong. 

Hypatia spun off of repose.catalog, but the documentation does not look complete. 

Repoze.catalog, looks pretty good, but also pretty dumb.  A simple interface change would make it much better.  The repose.catalog 
api mentions object id.  Duh.  Every object has an internal oid.  So instead of passing around object ids, just assume that the 
object id is the old, and then do not return object ids, but return the objects themselves .

Please make the interfaces as simple conceptually as possible. 

> 
> On Oct 28, 2017, at 8:15 PM, Jim Fulton <[email protected]> wrote:
> 
> I also wonder if it would be a good idea to add a hook to automate index updates, as an alternative to application event frameworks.  I'm thinking of a hook that takes an iterable of added and updated objects.

Some of the updated objects I want to index, some I do not.  Some I want to index in one catalog, some 
I want to update in another catalog.   Just let me do it myself. 

Warm Regards
Chris

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.