[Tickets #4881] IMSP backend - _read function's handling of id lists

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=4881
-----------------------------------------------------------------------
 Ticket             | 4881
 Created By         | noah at lsit.ucsb.edu
 Summary            | IMSP backend - _read function's handling of id lists
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Unconfirmed
 Priority           | 1. Low
 Owners             | 
+New Attachment     | turba-imsp-fix-read-multiple-ids.patch
-----------------------------------------------------------------------


noah at lsit.ucsb.edu (2007-01-12 11:08) wrote:

While not used this way by the _search function, Turba's IMSP backend's
_read function is designed to handle multiple input ids, returning
multiple results.  For it to work, the result needs to be reset during
each iteration (different contacts lack certain fields that would
otherwise be inherited from the previous entry).

The patch also includes a line to continue upon invalid entry, instead of
immediately returning a PEAR_Error.  A PEAR_Error is returned only if no
result is found for any id and getEntry has passed up a PEAR_Error.