Wildcard search fails

Question

Using DS 5.2 I have noticed some anomalies in search results using wildcards.
Searching, for example, for "pager=*1" returns all the correct entries but also all the entries with NO pager number specified. The same happens for any single int after the wildcard, (but not a double int. EG "pager=*99" returns the correct anticipated result set).
This also happens with other attributes such as homephone and email.
Has anyone else come across this?
Thanks in advance for any help.
Regards
DB

Answer 1

I have heard of this before but never seen it myself. I tend to use older, patched up versions of DS (e.g. 5.1SP3) for reasons just like this.
The previous cases were 1) a bug in the search algorithm was not handling wildcard searches with a small number of characters correctly if they were rooted at the beginning or the end of the string or 2) the indexes for multi-valued attributes were screwed up and the only solution was to get a patch and rebuild the indexes.
In both cases it was a bug. I think #2 implied that the entry had a previous value that matched the search, but the value had been deleted and the index was not updated properly. If this attribute is indexed you could try deleting the index and recreating it to see if the problem goes away.