Am Freitag, 6. Juli 2007 07:55 schrieb Pierangelo Masarati: > Wilhelm Meier wrote: > > Below are some additional questions. Any hints? > > > > Am Montag, 2. Juli 2007 09:31 schrieb Pierangelo Masarati: > >> Wilhelm Meier wrote: > >>> Yes, schema checking succeeds: > >> > >> OK > >> > >>> kmux-postgres:/etc/ldap# dpkg -l slapd > >>> ii slapd 2.3.30-5 OpenLDAP server (slapd) > >> > >> OK > >> > >>> In the log below (some lines after the log above) you see that it tries > >>> to set the attribute uidNumber for objectClass person - thats wrong!?! > >> > >> Don't be confised by LDAP vs. SQL. In that case, it is setting > >> uidNumber for the SQL person, which is not related to LDAP. It's your > >> mapping that defines what person contains. In back-sql, in fact, > >> entries are essentially based on a structural class, defined by means of > >> the mappings, which contains all attributes of that type of entry. > > > > What happens if my object has more than one structural objectclass > > (proposed that the structural classes share the same inheritance line)? > > Then back-sql searches the attributes in the mapping of the first(?) > > structural class? > > I don't have the answer right now; I suggest you read the code (you see, > this is the difference between open and closed source). In any case, > the more you go along that trail, the more you'll get hurt. Back-sql > should be intended the other way round: you've got some tables in SQL, > you want to render them nicely in LDAP. If your ambition is to > implement full LDAP semantics support in back-sql, well, good luck.
thanx > > p. > > > > Ing. Pierangelo Masarati > OpenLDAP Core Team > > SysNet s.r.l. > via Dossi, 8 - 27100 Pavia - ITALIA > http://www.sys-net.it > --------------------------------------- > Office: +39 02 23998309 > Mobile: +39 333 4963172 > Email: [EMAIL PROTECTED] > --------------------------------------- -- Wilhelm
