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

RE: "ldapsearch uid=ab" works "ldapsearch cn=a" doesn't in 2.1.19

To: "'Michael Dean'" <sysmwd@detir.qld.gov.au>, <openldap-software@OpenLDAP.org>
Subject: RE: "ldapsearch uid=ab*" works "ldapsearch cn=a*" doesn't in 2.1.19
From: "Howard Chu" <hyc@highlandsun.com>
Date: Tue, 13 May 2003 00:51:55 -0700
Importance: Normal
In-reply-to: <20030513160317.D95483@buffy.detir.qld.gov.au>

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

> hi
>
> I've just recently upgraded from 2.1.17 to 2.1.19 and I'm now having
> problems
> doing a one character plus wildcard search in 2.1.19.. ie.
>
> with two characters (or more) with the wildcard the search
> returns some
> data ...

Due to a bug in substring indexing that was fixed in 2.1.18 and 2.1.19, the
substring index format changed. You need to run slapindex to regenerate your
substring indexes. Sorry for this, the format change was unavoidable in order
to correct the bug.

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

Follow-Ups:
- RE: "ldapsearch uid=ab*" works "ldapsearch cn=a*" doesn't in 2.1.19
  - From: Michael Dean <sysmwd@detir.qld.gov.au>

References:
- "ldapsearch uid=ab*" works "ldapsearch cn=a*" doesn't in 2.1.19
  - From: Michael Dean <sysmwd@detir.qld.gov.au>

Prev by Date: RE: bdb_equality_candidates: (attr) index_param failed (18) ?
Next by Date: RE: bdb transaction logs don't disappear
Index(es):
- Chronological
- Thread

RE: "ldapsearch uid=ab*" works "ldapsearch cn=a*" doesn't in 2.1.19

RE: "ldapsearch uid=ab" works "ldapsearch cn=a" doesn't in 2.1.19