directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <>
Subject [jira] [Commented] (DIRSTUDIO-735) "Copy table" icon in the results page doesn't keep the rank of multivaluate attributes
Date Wed, 29 Jun 2011 11:29:28 GMT


Pierre-Arnaud Marcelot commented on DIRSTUDIO-735:

The big problem with this issue is that LDAP RFCs specify that for an entry, "the set of attribute
values is unordered".

RFC2251 -
"Each attribute value is distinct in the set (no duplicates).  The order of attribute values
within the vals set is undefined and implementation-dependent, and MUST NOT be relied upon."

RFC4511 -
"No two of the attribute values may be equivalent as described by Section 2.2 of [RFC4512].
 The set of attribute values is unordered. Implementations MUST NOT rely upon the ordering
being repeatable."

Now, of course, given a particular implementation you could expect to get the attribute values
always in the same order, but not necessarily.
I think ApacheDS does this for example, but I'm not sure it was ever guaranteed or intended.
This could be particularly difficult when working in an environment with various implementations
in place or when switching from one to another.

That said, I understand that it can be handy sometimes to rely on it.

We'll see what we could do about it...

> "Copy table" icon in the results page doesn't keep the rank of multivaluate attributes
> --------------------------------------------------------------------------------------
>                 Key: DIRSTUDIO-735
>                 URL:
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 1.5.3
>            Reporter: Pascal Espag.
>            Priority: Minor
> The "Copy table" icon present in the results page of an ldap search is usefull to export
the results by copy/paste.
> The issue is that the values of multivaluate attributes are sorted by alphabetical order
(not in the real order in LDAP).
> The rank of the values can be important (like in my case).
> Note that the export function keep the good rank for the multivaluate attibutes; the
issue is only about the "Copy table" function

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message