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

* Your Email Address
* Spam protection	Enter the letters below: ._..___.. .. . . \| _/ \| \|\| \| \| _\|_./__.\|__\|\|___\|__\|
Comment	> 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.
Attachment
Watch this ticket