Re: Server 2.3.4 & back-sql (+ back.c dif) cannot modify database

[Pierangelo Masarati <ando@sys-net.it>]

Ken Johanson wrote:

> Hello,
>
> I successfully built the server using the diff provided earlier by 
> Hallvard (thanks!) and I can now read from the database via LDAP, 
> however I cannot modify entries or attributes.
>
> In trace mode, I see the following:
>
>   backsql_modify(): modifying entry "cn=Torvlobnor 
> Puzdoy,dc=example,dc=com" (id=3)
> <= acl_access_allowed: granted to database root
> ==>backsql_modify_internal(): traversing modifications list
>    backsql_modify_internal(): modifying attribute "cn" (replace) 
> according to mappings for objectClass "inetOrgPerson"
>    backsql_modify_internal(): replacing values for attribute "cn"
>    backsql_modify_internal(): add procedure is not defined for 
> attribute "cn" - unable to perform replacements
>    backsql_modify_internal(): modifying attribute "entryCSN" (replace) 
> according to mappings for objectClass "inetOrgPerson"
>    backsql_modify_internal(): modifying attribute "modifiersName" 
> (replace) according to mappings for objectClass "inetOrgPerson"
>    backsql_modify_internal(): modifying attribute "modifyTimestamp" 
> (replace) according to mappings for objectClass "inetOrgPerson"
>
> The "add procedure is not defined for attribute "cn" - unable to 
> perform replacements" line seems to be the problem.
>
> Is there an additional 'insentry_stmt' type paramter that I would need 
> in slapd.conf?

No - insentry_stmt and similar are to customize __entry__ bookkeeping, 
not for data modification.  What you need is the add_proc in 
ldap_attr_mappings for the inetOrgPerson objectClass.  What RDBMS are 
you using, and where did you get the sample data from?  Data for 
PostrgreSQL is the most complete and actually passes all sql-test* in 
the test suite.  Did you succeed with that?

p.



   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497