http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1677 ------- Comment #2 from mason.james@liblime.com 2007-12-19 16:33 ------- -------------------------------------------------- OK, so a little more digging and some more output from the log.. with the same search. querying : ti=love on biblioserver at /opt/koha/production/intranet/modules/C4 /Search.pm line 1190. string :ti=love at /opt/koha/production/intranet/modules/C4/Search.pm line 125 leaf : ti=love return : 641,circleoflo-1;960,childcarea-1;993,loveisnote-1;1209,lovelaught-1;1229,howtoloveb-1;1510,siblingriv-1;1727,youregoing-1; for LEAF : ti=love at /opt/koha/production/intranet/modules/C4/Search.pm line 1428. querying : au=baker on biblioserver at /opt/koha/production/intranet/modules/C4/Search.pm line 1190. string :au=baker at /opt/koha/production/intranet/modules/C4/Search.pm line 1254. leaf : au=baker return : 641,circleoflo-2; for LEAF : au=baker at /opt/koha/production/intranet/modules/C4/Search.pm line 1428. ### $leftresult: '641,circleoflo-1;960,childcarea-1;993,loveisnote-1;1209,lovelaught-1;1229,howtoloveb-1;1510,siblingriv-1;1727,youregoing-1;' ### $rightresult: '641,circleoflo-2;' ### $operand: ' and ' ### $finalresult: undef ### $result: undef -------------------------------------------------- so it seems that the 2 searches (title and author), does correctly get a matching result for bib '641,circleoflo' but NZAnalyze() doesnt successfully return it, as the index differs slighty, so the match fails because the indexes have different end value (-1, -2) 641,circleoflo-1 641,circleoflo-2 what does this end value mean? mysql> select * from nozebra where biblionumbers like '641%'; | biblioserver | title | love | 641,circleoflo-1; | biblioserver | author | baker | 641,circleoflo-2; is this a bug in nozebra-search, or a bug in rebuild-nozebra.pl making buggy indexes? i think its a bug with the indexes, not the search... i havent yet worked out what the -1, -2 means yet? ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.