Summary: | Query... variables should be defined within loop in Search.pm | ||
---|---|---|---|
Product: | Koha | Reporter: | David Cook <dcook> |
Component: | Searching | Assignee: | Bugs List <koha-bugs> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | katrin.fischer, marjorie.barry-vila |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: |
Description
David Cook
2014-06-18 05:04:38 UTC
This is still a thing last time I checked... should fix this one of these days... David, can you tell if this is still valid and provide a little more information? (In reply to Katrin Fischer from comment #2) > David, can you tell if this is still valid and provide a little more > information? I haven't looked in a long time, but I'd imagine that it's still valid. I think an example is QueryAutoTruncate. When it's on, all the index/operand pairs should have truncation enabled. However, there are some indexes that don't support truncation, so they'll turn QueryAutoTruncate off. So in theory you could have something like this: Pair0-Truncated, Pair1-Can't truncate disable auto truncation,Pair2-NotTruncated, Pair3-NotTruncated When really it should be like this: Pair0-Truncated, Pair1-Can't truncate, Pair2-Truncated, Pair3-Truncated Apologies if that still sounds too vague. Pretty sure this is still a problem. One of these days I need to sit down and have a big search review... |