Description: ------------ If trying to replace an attribute on an LDAP entry that gets a new value of 0 (the number zero), the attribute is deleted instead of updated. This is because of the way PHP handles "0" as equal to NULL when only using two equality characters (==) instead of three. Test script: --------------- $new = array( "description" => 0, ); $entry->replace($new); $entry->update(); Expected result: ---------------- The attribute should be updated with the new value of "0" instead of be deleted. Actual result: -------------- On a required attribute I get this error: Failed to update entry: Could not delete attribute description: Object class violation: LDAP_OBJECT_CLASS_VIOLATION

The following patch has been added/updated: Patch Name: Net_LDAP2_Entry_replace Revision: 1249339855 URL: http://pear.php.net/bugs/patch-display.php?bug=16491&patch=Net_LDAP2_Entry_replace&revision=1249339855&display=1

Can you expand your test script to be properly executable (ie, instantiate $entry for us)? Can you do a new version of your patch, it's backwards ! :D

Thank you for your bugreport. The problem is, that the int 0 evaluates to both false and null, as you correctly described. When submitting "0", you should make sure, that you pass it as string, not as int, as LDAP attribute values are strings (at least, the description is). Conversion to the correct type is done on the LDAP server, so it is always safe to pass strings with numbers instead of real integers. Your patch could not be applied, because it imposes unknown results when for example true or false is passed. However, i introduced code into SVN which allows passing int(0); it gets converted to string("0") now. Try latest SVN or this: $new = array( "description" => "0", ); $entry->replace($new); $entry->update(); If the value is an variable, you can convert int to string: $string = "$int";

(fixed in svn)

The following patch has been added/updated: Patch Name: Net_LDAP2_Entry_replace Revision: 1249384986 URL: http://pear.php.net/bugs/patch-display.php?bug=16491&patch=Net_LDAP2_Entry_replace&revision=1249384986&display=1

@beni: I am unable to see why true or false might be a problem for applying the patch (which is now updated). If either true or false is set on an attribute, that is most likely, i believe, the value the user might expect to be updated on the entry as the string "1" or "". The documentation of the replace() method states this: "If the attribue value is null, the attribute will de deleted." I would expect any other value to be updated on the entry, even (bool)false.

The problem is, it is not defined. The doc says in the examples of the method documentation: "attr-name" => "single value", "attr-name" => array("multivalue1", "multivalue2") which references strigns. TRUE for example may update to string("true") or to boolean(true) or to int(1) - its not defined and may vary from server to server. Thats why it is left to you to properly call the method. Also note that phps ldap function ldap_modify() also expects it that way.