[Cosmo] Re: indexing all components in a calendar resource?

Brian Moseley bcm at osafoundation.org
Tue Feb 14 07:13:50 PST 2006


On 2/14/06, Cyrus Daboo <cyrus+lists.cosmo at daboo.name> wrote:

> As to indexing all the rest - well you do have to allow queries against
> anything, so one way or another you have to do that, but whether that is
> done by indexing everything, or only select components/properties is really
> up to you. If a client really does want to query some 'obscure' property
> (e.g. PRODID) I don't see why the server has to be as fast on that as all
> the rest. Note that many servers use a database backend rather than
> straight indexing, and often they choose to only have separate columns for
> select properties, putting all the rest in a 'catch-all'. So with those,
> queries against select properties will be fast, against others will be slow.

that's a reasonable compromise. thanks for the discussion, cyrus.



More information about the Cosmo mailing list