[symfony-users] Re: Zend Lucene Search - Parser problem

2010-10-20 Thread pghoratiu
By default Lucene search does not look for substrings, I think there are several reasons why they are doing this mostly related to performance. There are some tokenizer engines which put in the index the combination of all substrings and they solve this way the problem of substring search, example:

[symfony-users] Re: Zend Lucene Search - Parser problem

2010-10-20 Thread Adam
Thank you. I try it. If its too slow I'll change the Zend engine to sql queries (but it is more complex). On okt. 20, 02:16, Jonathan Franks wrote: > http://framework.zend.com/manual/en/zend.search.lucene.query-language... > > > Starting from ZF 1.7.7 wildcard patterns need some non-wildcard pref

Re: [symfony-users] Re: Zend Lucene Search - Parser problem

2010-10-19 Thread Jonathan Franks
http://framework.zend.com/manual/en/zend.search.lucene.query-language.html > Starting from ZF 1.7.7 wildcard patterns need some non-wildcard prefix. > Default prefix length is 3 (like in Java Lucene). So "*", "te?t", "*wr?t*" > terms will cause an exception > Zend_Search_Lucene_Search_QueryParse

[symfony-users] Re: Zend Lucene Search - Parser problem

2010-10-19 Thread Adam
Hi, Thx for your fast reply. Bad bad javascript :). Is there a way to search for word parts? example: search saw result chainsaw, woodsawlikething etc ( so its like *saw* but i get Error: At least 3 non-wildcard characters are required at the beginning of pattern. ) On okt. 19, 16:38, Jonathan Fr