Why do searches return only objects with fields that start with my query string, rather than containing the query string anywhere in the field?
This behavior is intentional. The search interface goes directly into an SQL query, and thus support SQL wild card characters. Unless you query for a string at the beginning of a column, the index on that column won’t be used. So we default to only searching at the beginning of a field in order to take advantage of the speed provided by an index. However, you can get around this functionality in two ways. You can by put a ‘%’ in front of your search string, thereby forcing the SQL query to be a full substring query. Or you can enable on the “FULL_SEARCH” bricolage.conf directive and restart Bricolage. But know that either of these methods will a lot slower (though you probably won’t notice much until you have 1000s of documents).
Related Questions
- When I use the Query string (qst) command in the Design Window, why do I see Fields called BLOCKID, SYMBOL and LSTYLE reported when these may not be in the data that is loaded?
- When I save objects to TSM servers, why don I see the names of the objects or the names of the libraries when I query the OS/400 filespaces on the TSM server?
- Why do searches return only objects with fields that start with my query string, rather than containing the query string anywhere in the field?
