This isn't CFC related, but I wanted to get this out there before I forget about it. I found an interesting behavior change today in CFMX. It's one that might cause you a lot of grief if you aren't aware of what's happening. The "behavior" has to do with EXPLICIT searches in Verity. There was a bug in previous versions of ColdFusion that caused explicit searches to actually execute as simple searches. What's the difference? Well, a simple search employs the STEM operator and MANY modifier by default. So, searching for test returns matches for test, tests, testing, tested, etc. An explicit search, however, does not employ STEM and MANY. So, a search for test returns only docs containing test, and not testing, tests, etc.

Now for the behavior change. Explicit searches are now working as intended in CF MX. This could cause problems for existing apps that are ported to MX, as well as new apps that are written that use explicit searches. There are really two parts to this issue. The first issue is that search terms have to be surrounded by quotation marks in explicit searches. So, the EXPRESSION="test" that works in a simple search throws an error when used in an explicit search. To search for test in an explicit search you have to code the search as EXPRESSION="'test'".

The second issue has to do with using various operators in an explicit search. In a simple search, using EXPRESSION="'f[eo]llow'" returns matches for fellow and follow only (note that stemming is off). Note the single quotation marks around the wildcard criteria. This syntax fails in an explicit search. In order to perform the same search in an explicit search, you must use the backquote (`) and not the single quote like this EXPRESSION="`f[eo]llow`". Even though the single quote works in a simple search, you should consider only using the backquote to ensure compatibility should you ever switch from a simple to an explicit search.