Since one of the main uses of Texis web scripting is designed to be processing user queries, in particular text search queries, and some queries have the potential to do a full table scan, which will really hurt performance, there are several query protection features built in to Texis. These are enabled by default when using Web Script, but not with tsql or the API.

If you are not getting the results you expect from a Vortex script you should always check for messages that are produced. By default these are HTML comments in the output. This means they are not directly visible to the user, but you can see them in the HTML source. If you have your own <putmsg> function in the script you can change the behavior of messages.

The default settings are fairly restrictive, and will only do searches that can be fully resolved using the index. The only potential for expensive processing is if your Metamorph index is not up to date. All the settings are individually settable with the <apicp> call. They are enabled by default so that you will need to explicitly disable them to change behavior, which is a good time to make sure you really want to do it.

The most common warnings you will see are "Query would require post-processing" and "Query would require linear search". There are a number of reasons that might cause a query to require post-processing. Using the special pattern-matchers and within processing will cause that. If you only have a Metamorph index, not Metamorph Inverted then phrases and LIKEP will also require post-processing. The linear search is required if you do not have an index, or the search can not use an index. You should first make sure you have the best index for the queries you are doing, and only then think about disabling the protection.

special pattern matchers, wildcards