You need to read the docs.
- wildcard=0 means that the query is *always* performed in a
non-exact way, applying regex style pattern matching. In other words:
the query is always performed as if the user had typed wildcards. For a
user typed string pippo, in regex notation this would be
data-match /pippo/.
- wildcard=1 means that the search is using wildcards (*) that the
user inserts - or not, like
*pippo : regex /pippo$/.
*pippo* : regex /pippo/
pippo : regex /^pippo$/
Typically useful in cases where there is a training for users and where
they are taught how to use the application.
all pattern matching is performed case-*IN*sensitive.
If you want to use full exact search specify wildcard=2 as of pm 3.2
beta. This should give you
data = pippo, case-sensitive. In most cases this is not very useful
and I have mainly foreseen it for searches with options or suggest.
This all is how it is intended to be, otherwise there is a bug ;-).
armin
ivan minčík wrote:
Armin,
I found that the search in postgis layer is always with wildcard. It is
not respecting
wildcard=0 or wildcard=1 in search.xml .
I just temporary replaced
$qs .= $valoperator $f ~* '$wc1$val$wc2' ;
by
$qs .= $valoperator $f = '$val' ;
to get it working without the wildcard.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users
