[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Display values of one attribute

To: Dave Horsfall <daveh@ci.com.au>
Subject: Re: Display values of one attribute
From: Jon Roberts <jon@mentata.com>
Date: Wed, 28 May 2003 05:52:47 -0500
Cc: OpenLDAP Software List <openldap-software@OpenLDAP.org>
In-reply-to: <20030528091549.B98976@mippet.ci.com.au>
References: <52E057CD4E1DD611B99F00805FE676CA86D88B@ffz00za5.ffz00e.mail.dresdner.net> <01b001c32455$751bc480$13ba430a@tmn.capgemini.fr> <20030528091549.B98976@mippet.ci.com.au>
User-agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.3.1) Gecko/20030425

Dave Horsfall wrote:

On Tue, 27 May 2003, Ha Minh NGUYEN wrote:

I would like to know what is the display order of one multivalue attribute ?
For example, the telephoneNumber attribute has 3 values, how they will be displayed in the ldapsearch command ? The oldest is the first ?

You cannot rely on the order.

I know I saw this in books and/or RFCs, but I have yet to see a multivalue attribute returned from any LDAP implementation with values not consistently in the order they are defined. I don't doubt the standard, but I have to ask: under what circumstances will OpenLDAP return values in an arbitrary order?

Jon Roberts
www.mentata.com

Follow-Ups:
- Re: Display values of one attribute
  - From: Dave Horsfall <daveh@ci.com.au>
- Re: Display values of one attribute
  - From: Frank Swasey <Frank.Swasey@uvm.edu>

References:
- rewrite userPassword-value with back-meta
  - From: "Gemeiner, Jan" <Jan.Gemeiner@dresdner-bank.com>
- Display values of one attribute
  - From: "Ha Minh NGUYEN" <haminh.nguyen@cgey.com>
- Re: Display values of one attribute
  - From: Dave Horsfall <daveh@ci.com.au>

Prev by Date: ldap_bind: Invalid credentials when loading initial entries
Next by Date: Dynamic Groups
Index(es):
- Chronological
- Thread