[Date Prev][Date Next]
Re: (ITS#3707) An unknown attribute in presence filter evaluates to (?=false) instead of (?=undefined)
At 02:51 AM 5/5/2005, firstname.lastname@example.org wrote:
>Full_Name: Pierangelo Masarati
>Submission from: (NULL) (188.8.131.52)
>Submitted by: ando
>An undefined attribute in a presence filter, e.g. "(undefined=*)", evaluates to
>"(?=false)", while in other filters, e.g. equality "(undefined=something)" it
>evaluates to "(?=undefined)". If there isn't any rationale behind it, I'd
>evaluate it to "(?=undefined)" as well, at least for consistency.
Though I disagree with the rationale behind the RFC 2251
requirement, the rationale for this slapd(8) behavior is
the RFC 2251 requirement.
The present match evaluates to TRUE where there is an attribute or
subtype of the specified attribute description present in an entry,
and FALSE otherwise (including a presence test with an unrecognized
I disagree as 'undefined' may be an unknown alias for a
present attribute description.