| Summary | IMSP backend - _read function's handling of id lists |
| Queue | Turba |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | noah (at) lsit (dot) ucsb (dot) edu |
| Created | 01/12/2007 (6772 days ago) |
| Due | |
| Updated | 01/13/2007 (6771 days ago) |
| Assigned | 01/12/2007 (6772 days ago) |
| Resolved | 01/13/2007 (6771 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Assigned
New Attachment: turba-imsp-read-searched-with-multiple-ids.patch
function's ability to handle a list of id's.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ IMSP backend - _read function's handling of id lists
Queue ⇒ Turba
New Attachment: turba-imsp-fix-read-multiple-ids.patch
State ⇒ Unconfirmed
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.