RE: LDAP query

["Griffith, Adrian, CON, OASD(HA)/TMA" <Adrian.Griffith@tma.osd.mil>]

The Netscape Directory 3.x has a referential integrity "plug-in".  "By
default, the referential integrity plug-in is enabled and set to perform
integrity updates on the member, uniquemenber, owner, and seeAlso attributes
immediately after a delete or rename operation".  It may be customized.

> ----------
> From: 	Andrew Probert[SMTP:AndrewP@rotek.com.au]
> Sent: 	Friday, November 13, 1998 1:15 AM
> To: 	ietf-ldapext@netscape.com
> Subject: 	RE: LDAP query
> 
> Hmm... referential integrity in a directory.
> 
> The only one I have seen that does this is OpenDirectory, which has a
> flag to turn on alias integrity checking, which is handled internally by
> the server.
> 
> Otherwise, one is up for handling all integrity issues in the client,
> especially since there is no concept of 'stored procedures' in a
> directory.  Is this a new standard in the making?
> 
> Andew Probert
> Rotek Consulting 
> a Division of Secure Network Services
> +61 3 9690 8877
> 
> > -----Original Message-----
> > From:	Raju Rajan [SMTP:raju@watson.ibm.com]
> > Sent:	Friday, November 13, 1998 12:10 AM
> > To:	ietf-ldapext@netscape.com
> > Cc:	ietf-ldapext@netscape.com
> > Subject:	LDAP query
> > 
> > 
> > Hi,
> > 
> >  I have a quick LDAP related question.
> > 
> >  In the Policy WG we have a schema where certain objects are
> > referenced from other
> > objects. The question relates to the deleting of objects, without
> > leaving dangling
> > references in the directory. The solutions we are considering are (a)
> > have a
> > ReferenceCount attribute or (b) have a ReferringDNList attribute, to
> > keep track of the
> > pointers to each object. Is there any way of getting around the
> > concurrent write problem?
> > That is, is there a way to "test and delete" as an atomic operation?
> > Thanks,
> > 
> > Regards,
> > 
> > Raju Rajan
>