Tickets :: [#155] LDAP Driver does extra work

6.0.0-alpha12

6/7/25

Summary	LDAP Driver does extra work
Queue	Turba
Queue Version	1.2.2
Type	Enhancement
State	Resolved
Priority	2. Medium
Owners	Horde Developers (at)
Requester	vincent.fiack (at) laposte (dot) net
Created	05/06/2004 (7702 days ago)
Due
Updated	08/26/2004 (7590 days ago)
Assigned	05/17/2004 (7691 days ago)
Resolved	08/26/2004 (7590 days ago)
Milestone
Patch	No

08/26/2004 12:35:19 PM	Jan Schneider	Comment #5 State ⇒ Resolved	Reply to this comment
No feedback.

08/16/2004 10:20:11 PM	Chuck Hagenbuch	State ⇒ Accepted

08/16/2004 10:19:44 PM	Chuck Hagenbuch	Comment #4 State ⇒ Stalled	Reply to this comment
That's definitely not a good solution, though. Can you be more specific about how it broke? Error messages? Anything?

08/16/2004 08:38:33 AM	leena (dot) heino (at) uta (dot) fi	Comment #3	Reply to this comment
The fix in the cvs broke the address book's address lists functionality. I was able to restore the address lists functionality by partially reverting the change in turba/lib/Sources.php between versions 1.36.2.8 and 1.36.2.9 Diff to restore address book's address lists functionality: --- turba/lib/Source.php.orig Fri Aug 13 10:25:42 2004 +++ turba/lib/Source.php Mon Aug 16 11:26:20 2004 @@ -213,7 +213,7 @@ require_once TURBA_BASE . '/lib/Object.php'; $list = &new Turba_List(); foreach ($remapped_results as $attributes) { - $list->insert(new Turba_Object($this, $attributes)); + $list->insert($this->getObject($attributes['__key'])); } $list->sort($sort_criteria, null, null, $sort_direction);

06/28/2004 12:30:03 AM	Chuck Hagenbuch	Comment #2 State ⇒ Resolved	Reply to this comment
Fixed in CVS for RELENG_1; this had already been fixed in HEAD, but it slipped through the cracks in terms of being backported until now.

05/17/2004 03:37:07 PM	Jan Schneider	State ⇒ Assigned Priority ⇒ 2. Medium Assigned to Horde Developers

05/06/2004 06:45:38 AM	vincent (dot) fiack (at) laposte (dot) net	Comment #1 Priority ⇒ 2. Medium Queue ⇒ Turba Type ⇒ Enhancement State ⇒ New	Reply to this comment
Hello, We use turba with ldap (openldap at first, a custom server now). It seems that each time we search an entry from the web interface, it lauches many queries : - a first one to get the user list corresponding to the search - a request by user to fetch its attributes (!) (those attributes have already been fetched in the first query, so why ask for it again ??) It looks like the first query is called by "search()", and the other ones by "read()"