directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Howard Chu <>
Subject Re: Renaming an entry with a case insensitive RDN : how to handle it ?
Date Thu, 16 Feb 2012 02:04:19 GMT
Emmanuel Lécharny wrote:
> Le 2/15/12 8:48 PM, Howard Chu a écrit :
>>> In this case I would suggest replacing
>>> the cn=john doe with cn=John Doe.
>>>      Q2 : if we modify the cn only, should the RDN be modified too ?
>>>      (currently, ADS does modify the CN, but not the RDN)
>> The op is a Mod[R]DN, so absolutely, the most obvious thing that
>> *should* happen is to change the RDN. It's less obvious how to change
>> the cn attribute. E.g., if the delOldRDN flag was set, then I would
>> expect a complete change, but if not set, maybe the correct result is
>> to have both "cn=john doe" and "cn=John Doe" in the entry.
> I don't see how possibly we can keep two values that are equals in the
> same attribute, considering that cn is case insensitive. Otherwise, how
> would you pull the right value when doing a search with "(cn=*oe)" ? Get
> twice the same entry ?

Right, Ludo already pointed this out in his reply, my mistake.

   -- Howard Chu
   CTO, Symas Corp. 
   Director, Highland Sun
   Chief Architect, OpenLDAP

View raw message