On Tue, 16 May 2006, Phillip J. Eby wrote:
To answer Grant's question, this does not actually keep Kind composition
"under the covers" - it's based purely on the annotation system. Annotation
attributes are normal attributes, so they should be as indexable as anything
else. However, if performance considerations show that storing stamp types
as a set (e.g. as shown above) is detrimental then some other way of tracking
active stamps is needed.
If everything is of the same kind, the kind query is going to be a lot less
useful. Currently, the kind query is used a lot...
As far as I know, we are not indexing any literal attributes at the moment
(other than via PyLucene). I had support for indexes of items having a value
for a given attribute in the repository and removed it since no one was using
it and it slowed commit down.
Of course, ref collections are natural indexes and we use those a lot (not
enough though)
Other than that we use indexes on abstract sets and these are always based on
ref collections and kind queries. Making everything of the same kind is
counter-productive in that context.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
