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

Re: back-sql and multiple objectclasses

Wilhelm Meier wrote:
> Hi,
> I have a problem using back-sql and entries with multiple object classes:
> If I add the entry:
> dn: cn=testuser2,dc=kmux,dc=de
> cn: testuser2
> sn: test
> objectClass: top
> objectClass: person
> objectClass: posixAccount
> gidNumber: 514
> uidNumber: 4711
> uid: test2
> homeDirectory: hh
> I get in the logs of slapd complains that attr uidNumber in objectClass person 
> is undefined. That's right, but the object has the additional class 
> posixAccount, which has the attribute.
> When I look in the logs, I see that the table ldap_entry_objectclasses gets 
> inserted the auxiliary class posixAccount AFTER it tries to set the attribute 
> uidNumber. So ist clear that it doen't find the attribute.

When data gets inserted in table should have nothing to do with
objectClass consistency.

Schema checking occurs __before__ doing anything else in add.  So I
assume that if a valid entry is passed, back-sql will not barf.  We need
to know what exactly slapd complains about.  And knowing what version of
OpenLDAP is creating trouble would be a good start.


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Email:   pierangelo.masarati@sys-net.it