[Tickets #4880] IMSP backend - Comma is inappropriate delimiter for cached list

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=4880
-----------------------------------------------------------------------
 Ticket             | 4880
 Created By         | noah at lsit.ucsb.edu
 Summary            | IMSP backend - Comma is inappropriate delimiter for cached list
 Queue              | Turba
 Version            | HEAD
 Type               | Bug
 State              | Unconfirmed
 Priority           | 2. Medium
 Owners             | 
+New Attachment     | turba-imsp-comma-name-fix.patch
-----------------------------------------------------------------------


noah at lsit.ucsb.edu (2007-01-12 10:38) wrote:

When the IMSP backend caches search results, it does so using comma as a
naive delimiter. Contacts whose name fields contain commas ("Doe, John")
don't show up when Turba uses the cached result. (Also causes the expected
invalid IMSP commands to be sent)

I've included a patch using '%,%' as a delimiter ... not sure if that's
what it should be, only sure that comma alone is bad.