[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Unexpected search latency on indexed field.



=> On Fri, 20 Dec 2002 14:18:47 -0500, asr@ufl.edu said:

> I think I am directing the indexing of all of these fields (or so I'll
> assert... )

I neglected to supply openLDAP version first time around: 2.1.5.

> [...]
> database	ldbm
> [...]
> index           cn                      pres,eq,sub
> index		mail			pres,eq,sub
> index		givenName		pres,eq,sub
> index		sn			pres,eq,sub
> [...]

> but I don't see a givenName.dbb.  I'm rebuilding the indices right now, just
> in case I've fotched something up there, but there's no givenName.dbb in the
> new db directory either.  All of these fields are present on most of the
> 750,000 objects in my database.

I see that givenName is defined as simply inheriting attributes from 'name',
but 'name' is defined in some unusual, implicit manner.  But 'sn' is defined
in substantially identical a manner..? 


## system schema
#attributetype ( 2.5.4.3 NAME ( 'cn' 'commonName' )
#       DESC 'RFC2256: common name(s) for which the entity is known by'
#       SUP name )

attributetype ( 2.5.4.4 NAME ( 'sn' 'surname' )
        DESC 'RFC2256: last (family) name(s) for which the entity is known by'
        SUP name )

 2.5.4.41 is defined above as it's used for subtyping
#attributetype ( 2.5.4.41 NAME 'name'
#       EQUALITY caseIgnoreMatch
#       SUBSTR caseIgnoreSubstringsMatch
#       SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )

attributetype ( 2.5.4.42 NAME ( 'givenName' 'gn' )
        DESC 'RFC2256: first name(s) for which the entity is known by'
        SUP name )


- Allen S. Rout