Something went wrong while setting issue due date.
Listing objects through objects::ls trigger a first search with scope 1
Closed
Listing objects through objects::ls trigger a first search with scope 1
Hello,
When listing object, for instance through the webservice, the log shows two LDAP search, one with scope 1 and one with scope 2 which is the actual search. The first one have a generic filter like @objectClass=*@ so it should use scope 0 as it only intends to test if the base exists.
(from redmine: issue id 5464, created on 2017-04-04, closed on 2017-04-24)
- Changesets:
- Revision fa07e955 by Côme Chilliet on 2017-04-04T13:03:54.000Z:
Fixes #5464 Using ldap_read instead of useless ldap_list for performance
- Revision cc8e399b2def6f9ccdef94654852a3e3e24e747e by Côme Chilliet on 2017-04-04T14:23:28.000Z:
Fixes #5464 Using ldap_read instead of useless ldap_list for performance
Conflicts:
include/class_ldap.inc
- Custom Fields:
- Bug in version: 1.0.19
- Support contract: Silver
- Dolibarr project Name: PJ1701-0027