Re: (ITS#4224) Incorrect return code from dyngroup/dynlist when checking membership of a non-existing DN?

[ando@sys-net.it]

On Mon, 2005-11-28 at 22:02 +0000, ando@sys-net.it wrote:
> I've found out that if I run a compare for "member:cn=Non-Existing" with either
> dyngroup or dynlist, I get noSuchObject (32) instead of FALSE.  The dynamic
> object correctly expands "memberURL" attributes into lists of "member"
> attributes, so the "member" attribute virtually exists, but the value doesn't,
> so backend_group() return noSuchObject, and this error is echoed in the result. 
> I think this is incorrect, because since "member" virtually exists, while  the
> asserted value is absent, the correct return code should be compareFalse.
> 
> I'd fix the code this way in the overlays unless there are objections.

I think the "error" is in backend_group(), but I'd leave that as is, so
that the caller can get more detailed info on the reason the operation
failed; the caller should be in charge of mapping the result to
something more appropriate with respect to the protocol operation it's
servicing.

p.




Ing. Pierangelo Masarati
Responsabile Open Solution

SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office:   +39.02.23998309          
Mobile:   +39.333.4963172
Email:    pierangelo.masarati@sys-net.it
------------------------------------------