[Date Prev][Date Next]
I assume that the base object of your search was located but
no objects within scope matched the filter. In this case,
an empty set of entries and result success is quite appropriate.
If this assumption is incorrect, please detail the operation
in more detail. In particular, duplicate the operation using
ldapsearch(1) and describe how ldapsearch(1) (and the C SDK)
handling differs from your client (and the Python SDK) differs.
At 03:07 PM 8/11/00 +0200, Michael Ströder wrote:
>I'm using ldapmodule for Python (linked against OpenLDAP 1.2.11).
>When using OpenLDAP 1.2.x server the module raises an exception
>ldap.NO_SUCH_OBJECT which is very handy. With OpenLDAP 2.0beta
>server ldapmodule returns an empty result list instead raising the
>exception which breaks existing code.
>Please review the answer of ldapmodule's author (see below) and
>check if there was anything changed in the LDAP response from 1.2.x
>to 2.0 in case an entry was not found.
>-------- Original Message --------
>Subject: Re: Behaviour when object is not found
>Date: Fri, 11 Aug 2000 21:53:53 +1000 (EST)
>From: David Leonard <firstname.lastname@example.org>
>To: Michael Ströder <email@example.com>
>CC: python-ldap-dev <firstname.lastname@example.org>
>On Fri, 11 Aug 2000, Michael Ströder typed thusly:
>> With OpenLDAP 2.0beta ldapmodule returns an empty result list
>> instead which breaks existing code. I would expect that this is more
>> a OpenLDAP 2.0 issue but before I start a discussion on
>> email@example.com I would like to understand exactly under
>> which conditions the exception ldap.NO_SUCH_OBJECT is raised.
>if ldap_search() or ldap_result() returns -1 AND the LDAP structure
>has its ld_errno field set to NO_SUCH_OBJECT, then that exception is
>David Leonard David.Leonard@csee.uq.edu.au