Full_Name: Martin Evans Version: 2.0.4 OS: Solaris and Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (138.37.8.180) Fuzzy Matching in 2.0.4 appears not to work very well. Approx searches for entries return no results e.g. An exact match returns ok... [root@mdte-pc openldap]# /usr/local/bin/ldapsearch -H "ldap://localhost:389" -x -LLL "(sn~=holman)" dn: cn=J G Holman, ou=Computing Services, o=Queen Mary and Westfield College,c =GB objectClass: top objectClass: person objectClass: organizationalPerson objectClass: newPilotPerson objectClass: labeledURIObject cn: J G Holman cn: Dr Holman cn: John Holman ou: Computing Services sn: Holman postalAddress: Queen Mary & Westfield College $ Mile End Road $ London $ E1 4N S mail: J.G.Holman@qmw.ac.uk facsimileTelephoneNumber: +44 20 8980 2001 title: Head of Central Servers roomNumber: Queens' CB207 telephoneNumber: +44 20 7882 5323 labeledURI: http://www.css.qmw.ac.uk/ but any other mispellings return nothing.... "(sn~=hollman)" "(sn~=holmun)" "(sn~=holmen)" "(sn~=holmann)" only "(sn~=holman)" seems to work. Ive tried the --enable-phonetic configure option. It made no changes. Cheers, Martin.
At 03:27 PM 10/4/00 +0000, m.d.t.evans@qmw.ac.uk wrote: >Full_Name: Martin Evans >Version: 2.0.4 >OS: Solaris and Linux >URL: ftp://ftp.openldap.org/incoming/ >Submission from: (NULL) (138.37.8.180) > > >Fuzzy Matching in 2.0.4 appears not to work very well. >Approx searches for entries return no results >e.g. An exact match returns ok... The current approx matching code just uses equality matching. Phonetic/Soundex (or other) approximate matching codes need updating... the --enable-phonetic config option is a no-op at present. Kurt
"Kurt D. Zeilenga" wrote: > > At 03:27 PM 10/4/00 +0000, m.d.t.evans@qmw.ac.uk wrote: > >Full_Name: Martin Evans > >Version: 2.0.4 > >OS: Solaris and Linux > >URL: ftp://ftp.openldap.org/incoming/ > >Submission from: (NULL) (138.37.8.180) > > > > > >Fuzzy Matching in 2.0.4 appears not to work very well. > >Approx searches for entries return no results > >e.g. An exact match returns ok... > > The current approx matching code just uses equality matching. > Phonetic/Soundex (or other) approximate matching codes need > updating... the --enable-phonetic config option is a no-op > at present. How high is this on your priority list? Is it likely to be fixed? Martin. -- M.D.T.Evans - Computing Services - Queen Mary & Westfield College --
At 03:54 PM 10/4/00 +0000, M.D.T.Evans@qmw.ac.uk wrote: >"Kurt D. Zeilenga" wrote: >> >> At 03:27 PM 10/4/00 +0000, m.d.t.evans@qmw.ac.uk wrote: >> >Full_Name: Martin Evans >> >Version: 2.0.4 >> >OS: Solaris and Linux >> >URL: ftp://ftp.openldap.org/incoming/ >> >Submission from: (NULL) (138.37.8.180) >> > >> > >> >Fuzzy Matching in 2.0.4 appears not to work very well. >> >Approx searches for entries return no results >> >e.g. An exact match returns ok... >> >> The current approx matching code just uses equality matching. >> Phonetic/Soundex (or other) approximate matching codes need >> updating... the --enable-phonetic config option is a no-op >> at present. > >How high is this on your priority list? It's not even on MY (personal) priority list. Others, however, have voiced that it is on THEIR (personal) priority lists. >Is it likely to be fixed? Note that implemented approximate matching isn't broken per LDAP/X.500 specifications. I do, however, suspect someone will add improved approximate matching eventually. Those interested in working on such should cooridinate activities on the developer's mailing list. Kurt
changed notes changed state Open to Suspended moved from Incoming to Software Enhancements
moved from Software Enhancements to Development
changed notes
changed state Suspended to Closed
being worked by Mark Adamson