Looking at ways to increase the performance of search options being used by users, the index option “full-text” crossed my eyes. Reading up on what it does and how it works, I am not entirely sure what the intended purpose is in the Thinkwise product.
I was hoping I could use it for the combined filter, but those make “LIKE” statements on the view/tabel it is used on and for full-text it needs “CONTAINS”.
Could someone enlighten me?
I am also open to hear about cases where someone has used the full-text in his/her functionality to get an idea of how it might benefit.
Solved
What are intended use of the Full-Text index option?
- Superhero
- 116 replies
Best answer by Anne Buit
Hi Mark,
Currently, the full-text index can only be used in views and application logic.
The solution proposed by the following idea would allow for combined filter input to be mapped into a CONTAINS clause.
1 person likes this
This topic has been closed for replies.
+5Hi Mark,
Currently, the full-text index can only be used in views and application logic.
The solution proposed by the following idea would allow for combined filter input to be mapped into a CONTAINS clause.
1 person likes this
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.