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

6.0.0-beta1

9/24/25

Summary	IMSP backend - Comma is inappropriate delimiter for cached list
Queue	Turba
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	mrubinsk (at) horde (dot) org
Requester	noah (at) lsit (dot) ucsb (dot) edu
Created	01/12/2007 (6830 days ago)
Due
Updated	01/13/2007 (6829 days ago)
Assigned	01/12/2007 (6830 days ago)
Resolved	01/13/2007 (6829 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

01/13/2007 04:24:31 AM	Michael Rubinsky	Comment #4	Reply to this comment
...um, make that using serialize() / unserialize() instead...

01/13/2007 04:02:37 AM	Michael Rubinsky	Comment #3 State ⇒ Resolved	Reply to this comment
Committed, using a NULL delimiter instead. Thanks

01/12/2007 06:52:08 PM	Jan Schneider	Comment #2	Reply to this comment
I didn't look at the code, but it might be useful to cache an array or a NUL separated list instead.

01/12/2007 06:42:29 PM	Chuck Hagenbuch	State ⇒ Assigned Assigned to Michael Rubinsky

01/12/2007 06:38:59 PM	noah (at) lsit (dot) ucsb (dot) edu	Comment #1 Priority ⇒ 2. Medium Type ⇒ Bug Summary ⇒ IMSP backend - Comma is inappropriate delimiter for cached list Queue ⇒ Turba New Attachment: turba-imsp-comma-name-fix.patch State ⇒ Unconfirmed	Reply to this comment
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.