On 19/1/05 8:09 pm, sharib <[EMAIL PROTECTED]> wrote:

> 
> 
> Hi,
> 
> I am having a weird problem with the ldap search filter. Here it is
> 
> when using the filter (&(Title=training*)(Owner=*e7001*)), i get 1
> result out of the total of 2 entries that i should get. One entry that
> is being missed is however returned when the use the following filter
> 
> (&(Title=training*)(Owner=e7001))  - basically remove the *s from the
> e7001.
> 
> Why is this happening. Shouldnt the * filter include the second case.
> Please advise

How the server matches your filter depends entirely on the matching rules it
implements for the attributes you're using.

In the standard schema, the owner attribute uses the DN syntax (actually it
is a subtype of an attribute using the DN syntax). An equality matching rule
is defined for this attribute, but because DNs aren't strings there is no
substring matching rule defined.

If you're using standard schema, then that's the reason you're getting
inconsistent results. I'd have hoped your two searches would return some
sort of error instead, because you're trying to match a non-DN value.

If you're not using standard schema, then you need to look at what matching
rules are defined for the attributes you're using.

Cheers,

Chris


Reply via email to