Status

Directory
PerLDAP
P3
normal
RESOLVED FIXED
19 years ago
a year ago

People

(Reporter: Leif Hedstrom, Assigned: Leif Hedstrom)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

19 years ago
While perusing the http://www.perldap.org docs, I noticed that the docs
for the conn module contain the following error:

modifyRDN

       This will rename the specified LDAP entry, by modifying it's RDN.
For example:

           $rdn = "uid=fiel, ou=people, dc=netscape, dc=com";
           $conn->modifyRDN($rdn, $entry->getDN());

Should be something like:

modifyRDN
       Assume a DN of "uid=leif, ou=people, dc=netscape, dc=com" that
you want to rename to
       "uid=fiel, ou=people, dc=netscape, dc=com".
       This will rename the specified LDAP entry, by modifying it's RDN.
For example:

           $rdn = "uid=fiel";
           $conn->modifyRDN($rdn, $entry->getDN());

If you do it by the docs, you'll get an operations error (vbecause it
only wants the RDN attribute, not the whole DN).

Also, LDAPMODIFY provides for a "deleteoldrdn" parmameter.  This allows
you to specify whether or not to delete the attribute associated with
the old RDN.  Does the PerLDAP function have such functionality?  I see
that the default behavior is equivilant to "deleteoldrdn: 1" (nuke the
old RDN attribute from the entry).  This is probably the best default
(since it's what you would probably want to do most of the time anyway).
 But, it might be nice (if it's not there) to have the option to leave
the old attribute intact.


Secondly,

In the Entry module docs:

setDN

Set the DN to the specified value. Only do this on new entries, it will
not work well if you try to do this on an existing entry. If you wish to
renamed an entry, use the

Should read:

Set the DN to the specified value. Only do this on new entries, it will
not work well if you try to do this on an existing entry. If you wish to
rename an entry, use the

(i.e. remove the "d" from the word "renamed").

Bob
(Assignee)

Updated

19 years ago
Status: NEW → ASSIGNED
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.