Feature #5219
Feature #1585: add conversion and runtime support for word indexes
further word index and CONTAINS improvements
0%
History
#1 Updated by Eric Faulhaber about 3 years ago
- Subject changed from improve word index and CONTAINS performance to further word index and CONTAINS improvements
With #1587, we have provided first class support for the word index and CONTAINS operator, including parsing/indexing the content of word indexed columns, better sorting for results of CONTAINS-based queries, and improving the performance significantly over the previous, UDF-based approach.
This task serves as a placeholder for further work to improve the performance of CONTAINS queries and word indexed fields and any other refinements to word index and CONTAINS support.
The exploration and possible use of database native support to implement CONTAINS support is considered part of this effort, unless other improvements can be devised to bring the performance of the current implementation more in line with that of the 4GL's implementation.
We also need to review edit 3821c/12004, which changed the index selection portion of query conversion to ignore word indices. I am concerned this change may have had unwanted side effects to downstream conversion, besides removing the unwanted effect on the ORDER BY clause of the target query.
#2 Updated by Igor Skornyakov about 3 years ago
Eric Faulhaber wrote:
We also need to review edit 3821c/12004, which changed the index selection portion of query conversion to ignore word indices. I am concerned this change may have had unwanted side effects to downstream conversion, besides removing the unwanted effect on the ORDER BY clause of the target query.
Actuallу, after recent changes regarding sorting restoring the logic with word indices selection, should be easy. Moreover, it can make the logic for deciding if the word table should be selected for implicit sorting more consistent.