Colon in advanced search term causes empty result set
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When an search term used in an advanced search includes a colon, the search always returns zero results - even if the basic search with the same term returns results.
I have confirmed that the problem is in (at least) Evergreen 1.4.0.7 (? - whatever GAPines is currently running) and 1.6.0.0 (BC Sitka), searching for the items 'me cheeta: my life', and 'lies: and the lying liars who tell them'. In both cases, basic search returns at least one result, and advanced search returns an empty result set.
Here's the logging for the OpenSRF call for the basic search.
2010-01-12 22:54:08 app2-2 open-ils.search: [INFO:19329:
And the advanced search:
2010-01-12 22:56:06 app1-2 open-ils.search: [INFO:27734:
It appears the problem may be that whatever is generating the search call in advanced search is not separately quoting the term 'lies: and the lying lairs who tell them', while the basic search is. I tested with the term 'harry potter' in basic and advanced searches in 1.6.0.0, and the quoting difference is the same. The combination of incomplete quoting and blocking characters may be to blame, but this is as far as I can take this issue.
installation specs: Sitka (EG 1.6.0.0, OpenSRF 1.2.0, Postgres 8.3.x, Ubuntu Hardy); and Pines (don't know)
Changed in evergreen: | |
status: | New → Fix Committed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
PINES is currently running EG 1.4.0.7, OpenSRF 1.0.7, Postgres 8.1.11, and Debian Etch, FYI