OK, forget it.
-----Message d'origine----- De : Pierangelo Masarati [mailto:ando@sys-net.it] Envoyé : jeudi 23 octobre 2008 16:13 À : emmanuel.duru@atosorigin.com Cc : openldap-its@openldap.org Objet : Re: (ITS#5769) Behaviour of ldap_sort_entries on a multivalued attribute
emmanuel.duru@atosorigin.com wrote:
Currently, ldap_sort_entries when used with a multivalued attribute
assumes that
the attribute values are in the same order for all the entries. It would
be
better if this was not the case. For example, I would like to use ldap_sort_entries to sort entries
according to
objectclass attribute, so as to group entries by kind of objects. Let be 3 entries: ==>cn=n1, objectclass: person, organizationalperson ==>ou=ou1, objectclass: organizationalunit ==>cn=n2, objectclass: organizationalperson, person result of ldap_sort_entries on objectclass: n2, ou1, n1, whereas I
expected n1,
n2, ou1.
ldap_sort_entries() is deprecated. As a consequence, I would not expect any activity on it. It is the client's duty to sort the way it likes.
p.
Ing. Pierangelo Masarati OpenLDAP Core Team
SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it
Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando@sys-net.it
-
emmanuel.duru＠atosorigin.com