Re: LDBM slapadd accepts orphaned entries (ITS#3339)

[Kurt@OpenLDAP.org]

This behavior is intended as the slapadd(8) purpose is to
restore a complete LDIF dump produced by slapcat(8), and
that dump might not be ordered.  One could add an option
to enable a parent check.  Historically, slapadd(8) (and
its predecessor, ldif2ldbm, performed less consistency
checks than done for protocol add operations.

Kurt

At 06:47 PM 9/19/2004, h.b.furuseth@usit.uio.no wrote:
>Full_Name: Hallvard B Furuseth
>Version: HEAD
>OS: 
>URL: 
>Submission from: (NULL) (129.240.186.42)
>Submitted by: hallvard
>
>
>slapd.conf:
>  include    /scratch/hbf/etc/openldap/schema/core.schema
>  database   ldbm
>  directory  /scratch/hbf/var/openldap-data
>  suffix     dc=uio,dc=no
>  index      objectClass eq
>
>test.ldif:
>  dn: ou=foo,ou=bar,dc=uio,dc=no
>  objectClass: organizationalUnit
>  ou: foo
>
>OTOH, BDB catches the error.  I haven't checked HDB.
>Maybe the bug was introduced when BDB slapadd was modified to accept
>entries out of order?