RE: objectclass index

["Howard Chu" <hyc@highlandsun.com>]

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Daniel Tiefnig

> "Kurt D. Zeilenga" wrote...:
> > NO! you should always have an equality index on objectClass,
> > other referral management (even when you have no referral objects)
> > will not have index support.
>
> hmm, thought that you'll have another opinion on this one, kurt.. but
> how's about howards announce of the patch:
>
> quoting "howard chu":
> | Ah yes. In that case, you might as well use the eq index. I don't
> | know if the patch will be in 2.0.19, but I have corrected this
> | behavior in the development stream. If your search does not include
> | the objectclass attribute in the filter, then those additional
> | objectclass tests(referral and alias) will not occur. (They are
> | superfluous when nothing else in the filter references
> | objectclass.)
>
> you agree with that, or does this contradict with your understanding
> of how referrals should be handled by slapd..?
> (i'm a bit confused at the moment.. :o)

Considering that Kurt wrote the internet draft that defines how referrals
are handled, I guess I'll have to go with Kurt's understanding of such.

The case I was thinking of that actually applies is when the user filter
specifies "objectclass=*" (objectclass present) in which case the hardcoded
test for objectclass=referral is unnecessary.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support