Global Text Search (Wildcard character?)

[benn32]

Does anyone know what character is used for 'wildcard' searches for the Global Text Search? I've tried "*" and "%" w/ out success.
Thanks!

[rufus_mills]

I can't find anything to suggest this is possible (hopefully I will be wrong!). If you think about internet search engines in general they don't usually support wildcards and I suspect the engines are based on similar tech.

Of course you could construct queries using 'contains' if you knew which tables and fields you wanted to search.

[#3]

I can't remember which open source engine Global Search runs on, but yeah Rufus is correct; the behaviour is more like internet search, not file search.

Plus in System Properties > Global Text Search the default max results per table query is 10. I'd assume you would start to run into performance issues if you set this to a very high value.

If you know which table you're interested in, don't use Global Search. Instead, just do a Search for Text (keywords) on that table alone. You'll get all matches returned, and a more speedier result.

[CapaJC]

The text index engine is Lucene.

In /demo, when I search for net*, I get results containing network.

When I search for net?ork, I get results containing network (so I think ? can be used to represent a single character).

I think the 10 matches per table default stems from a few ideas:
1) if a user doesn't see their result in the first 10 matches, they'll refine their search terms. I know I do in Google; I never page to the 2nd 10 matches.
2) longer lists of results in the results page look uglier
3) since it's really just building a separate list for each table's results, the less it has to render the better
4) a user can simply click the Incidents section header in the results page if they want to go to a full list of Incident matches for their search terms.

But we also realized some customers might wish to customize that limit of 10, hence the property.

[benn32]

If you type *work , you won't get any results. Actually it barks at you because "you cannot use a * or ? symbol as the first character of a search."