Romain Delalande a écrit :
> Ok Olivier, Thank you very much for this help.
> 
> Just another 2 words :
> - I know the behaviour I am expecting is kind of "unnatural", and that the 
> plugin has surely not been designed in order to fill that need
> - I understood the way to get a solution to my problem, and thank you for the 
> few tips, but there is just one thing I could not get :
> " and then use the myprefix:myindexedfield = 'lucene' query."
> 
> Where is that configuration ? Are you talking about the operator in the 
> contribution to QueryModelService :
> 
> <queryModel name="byCustomNavQueryModel" docType="Custom_QueryNav">
> 
>      <max>10</max>
>       <whereClause>
> 
>         <predicate parameter="th myprefix:myindexedfield " operator="FULLTEXT 
> ONE OF">
>           <field schema="querynav" name="subjects" />
>         </predicate>
> </queryModel>
> 

My guess would be to use the '=' operator instead of 'FULLTEXT ONE OF' in the
previous configuration, provided that you configure myprefix:myindexedfield to
be indexed with an index of type 'Text and that the tokenizer treat '/' as word
seperators (i.e. in the same way as ' '). In that case the = operator on a Text
index means the 'lucene' word occures in the {'PHP', 'lucene'} bag of words if I
remember correctly. Again please check by running the raw NXQL queries in the
default advanced search form of nuxeo with the Administrator accounts to check
that behavior.

-- 
Olivier

_______________________________________________
ECM mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm

Reply via email to