Tickets :: [#7983] Search across multiple fields

6.0.0-beta1

7/17/25

Summary	Search across multiple fields
Queue	Turba
Queue Version	2.3.1
Type	Bug
State	Resolved
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	matt1 (at) clara (dot) co (dot) uk
Created	02/13/2009 (5998 days ago)
Due
Updated	07/10/2009 (5851 days ago)
Assigned	02/15/2009 (5996 days ago)
Resolved	07/10/2009 (5851 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/10/2009 12:41:23 AM	Michael Rubinsky	Comment #10 Taken from Horde Developers State ⇒ Resolved	Reply to this comment
Some of the changes that fixed this bug were never merged into the stable branch from HEAD. Now, almost a year to the day later, it's fixed. http://lists.horde.org/archives/cvs/Week-of-Mon-20090706/088400.html Thanks for the report.

07/09/2009 11:54:56 PM	Michael Rubinsky	Comment #9	Reply to this comment
Ok. Thank you for the info. This sounds like maybe a regression of what was fixed in ~~Bug: 6796~~ or perhaps all cases were not fixed.

07/09/2009 11:44:18 PM	matt1 (at) clara (dot) co (dot) uk	Comment #8	Reply to this comment
Yes it seems OK however I had to make the separate array and choose that in the prefs to tell the search to use it - it works great though now.. just not by default out of the box.

07/09/2009 11:43:00 PM	Michael Rubinsky	Comment #7	Reply to this comment
So it does work across multiple fields for you, just not the three specific fields in your name composite field?

07/09/2009 11:32:42 PM	Michael Rubinsky	Comment #6	Reply to this comment
FWIW, this works as expected in Git Master. ..and of course, by Git Master, I really meant CVS HEAD Turba along with Git Horde etc... sigh

07/09/2009 11:29:45 PM	matt1 (at) clara (dot) co (dot) uk	Comment #5	Reply to this comment
I solved this myself by using a separate array to search against.... 'name' => array('fields' => array('firstname', 'lastname', 'nameSuffix'), 'format' => '%s %s %s', 'parse' => array( array('fields' => array('firstname', 'lastname', 'nameSuffix'), 'format' => '%s %s %s'))), 'namesearch' => array('fields' => array('firstname', 'lastname'), 'format' => '%s %s', 'parse' => array( array('fields' => array('firstname', 'lastname'), 'format' => '%s %s'))),

07/09/2009 11:27:48 PM	Michael Rubinsky	Comment #4	Reply to this comment
FWIW, this works as expected in Git Master. I remember writing the code that creates OR searches with the search terms against each element in a composite field, but I don't immediately see why it's broken in FW_3. I'll see if I can track it down.

02/15/2009 05:10:01 AM	Chuck Hagenbuch	Comment #3 State ⇒ Assigned Assigned to Horde Developers Assigned to Michael Rubinsky	Reply to this comment
Confirmed.

02/13/2009 01:31:46 PM	matt1 (at) clara (dot) co (dot) uk	Comment #2	Reply to this comment
Apologies, forgot to say - this is with using SQL address book (MySQL).

02/13/2009 12:22:12 PM	matt1 (at) clara (dot) co (dot) uk	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Search across multiple fields Queue ⇒ Turba Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
When using search, if I enter a "firstname SPACE partial last name", eg "Matt St" which should match "Matt Stephenson", it doesnt match any results.. same behaviour in the autocompleter in IMP/DIMP.