Thierry Florac wrote:
>  - generally speaking, is it better to keep a single "big catalog", or a
> set of many catalogs, each of them indexing a smaller set of classes ? I
> suppose that querying is more simple with a single catalog, but what
> about general performances ??

With the hurry.query package it's just as easy to query across multiple
(named) catalogs.  I prefer to avoid monolithic catalogs with lots of

>  - I have to index "main content", but also "reference" classes which
> are used to classify my main content (example : I describe "forests" in
> a first step and afterwards, my main contents can be affected to one or
> more forests). In such a case, I want to make queries concerning forests
> themselves, but also queries about main content concerning forests they
> are attached to (to get, for example, every subject attached to a given
> forest). In this case also, is it better to keep track of the reference
> itself (myContent.forest = myForest) or of an attribute of the reference
> (myContent.forestId = myForest.uniqueId) ??
>  - perhaps a stupid question, but what's the best method to get the
> equivalent of Zope2's "meta_type" indexing, to only get instances of a
> given class, when queried indexes are applied to several classes
> (example : I use adapters to handle workflow publication on a wide set
> of classes, and I want to retrieve contents of a given class in a given
> workflow step) ??

Zope3-users mailing list

Reply via email to