<switching to devel mailing list>
Ok, this isn't so cool anymore, "attribute provided more than once" is breaking more of my client code when run against 2.0.23. I am using the contrib/ldapc++ code, and it is easy to get multiple attributes in that code.
Looking in servers/slapd/add.c there is a new line
if (!repl_user) {
*text = "attribute provided more than once";
return LDAP_TYPE_OR_VALUE_EXISTS;
}
a bit earlier:
repl_user = be_isupdate(be, op->o_ndn);
and inside be_isupdate, my be->be_update_ndn is null and op->o_ndn is the full DN of the object I am attempting to add.
It looks as if repl_user is zero because be->be_update_ndn is NULL. Can anyone please tell me why I am having this problem?
-----Original Message-----
From: Jeff Costlow
Sent: Tuesday, March 05, 2002 12:20 PM
To: 'openldap-software@openldap.org'
Subject: attribute sent multiple times
My client code just broke against 2.0.23 slapd, I don't think it exhibited this behaviour with 2.0.21, and I know it wasn't this way with 2.0.19.
Essentially my code is building an LDAPMod* that had multiple entries for objectClasses.
2.0.23 slapd started returning 0x14 "Type or Value Exists" complaining about the same attribute sent multiple times.
I was able to fix the problem by building my LDAPMod with one entry (with multiple values) for objectClass, but I'm curious why the change happened. Was my previous code non-compliant?