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

RE: Duplicate cn entries



On Thu, 2003-05-15 at 13:28, Howard Chu wrote:
> > -----Original Message-----
> > From: owner-openldap-software@OpenLDAP.org
> > [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of David Smith
> 
> > Yes, I know that. What I was trying to ask was whether
> > OpenLDAP ensures
> > that no two entries for an attribute can be identical, like so:
> >
> > dn: cn=Johnny Doe,ou=People,dc=example,dc=com
> > objectClass: person
> > cn: joe
> > cn: joe
> > sn: Doe
> >
> > >From my tests, I can get the above to work with ldap_modify and
> > ldap_mod_add, but _not_ ldap_add. That seems inconsistent to
> > me. What is
> > the _general_ rule for duplicate, identical entries for one attribute?
> > Can they exist or not?
> 
> This sounds like a bug in OpenLDAP 2.0, duplicate values of an attribute
> should not exist. OpenLDAP 2.1 definitely disallows this situation.
> 
> By the way, it would help the discussion to clarify the terminology.
> "Entries" have a set of attributes. "Attributes" have a set of values. A
> statement about "no two entries for an attribute can be identical" is rather
> confusing; you should be talking about "no two values for an attribute.

Excellent. Thanks for the clarification!

>   -- Howard Chu
>   Chief Architect, Symas Corp.       Director, Highland Sun
>   http://www.symas.com               http://highlandsun.com/hyc
>   Symas: Premier OpenSource Development and Support
-- 
Dave Smith
System Programmer, BYU CS Department
GPG Fingerprint: F907 A5C6 17AE C55D CE33  9F05 A829 B63C 99AE 2919