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_QueryParserExceptionZend_Search_Lucene_Exception .
> 
> It can be altered using 
> Zend_Search_Lucene_Search_Query_Wildcard::getMinPrefixLength() and 
> Zend_Search_Lucene_Search_Query_Wildcard::setMinPrefixLength() methods.       
>   
> 

So, it looks like you might be able to set it to 0. But I guess there is a 
reason that they have the prefix. Maybe performance related? not sure.

Good luck!



On 19 Oct 2010, at 16:15, Adam wrote:

> 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 Franks <jonat...@ifranks.com> wrote:
>> Hi Adam,
>> 
>> The chapter after search adds implements getting the results by ajax.
>> 
>> The javascript that sends the request adds an asterisk (*) to the end of the 
>> search query.
>> 
>> You can add asterisks to the ends of the words in the user search query.
>> 
>> On 19 Oct 2010, at 10:59, Adam wrote:
>> 
>>> Hi
>> 
>>> I integrated Zend Lucene Search to my project ( following the Jobeet
>>> tutorial ), index: one field (manufacturer name).
>>> The problem is that it only finds exact words, in the jobeet demo it
>>> finds it even if the input is a part of a word or just a letter.
>>> It look like the input isnt formatted but it's not formatted in the
>>> jobeet demo either( i downloaded the source ) - if i write stan* it
>>> finds stanley, but for stan nothing.
>>> I dont know what could be the problem, i did the same as they did in
>>> the tutorial, do i have to configure the search engine which is
>>> missing from the tutorial?
>> 
>>> Btw it is a webshop and there will be 60 000 products (5-10 index
>>> fileds), is this engine fast enough for me?
>> 
>>> (Sorry for my english)
>> 
>>> --
>>> If you want to report a vulnerability issue on symfony, please send it to 
>>> security at symfony-project.com
>> 
>>> You received this message because you are subscribed to the Google
>>> Groups "symfony users" group.
>>> To post to this group, send email to symfony-users@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> symfony-users+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/symfony-users?hl=en
> 
> -- 
> If you want to report a vulnerability issue on symfony, please send it to 
> security at symfony-project.com
> 
> You received this message because you are subscribed to the Google
> Groups "symfony users" group.
> To post to this group, send email to symfony-users@googlegroups.com
> To unsubscribe from this group, send email to
> symfony-users+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/symfony-users?hl=en

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en

Reply via email to