Bug #4752
Possible broken sort clause with word indexes
Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:
0%
billable:
No
vendor_id:
case_num:
version:
History
#1 Updated by Ovidiu Maxiniuc almost 4 years ago
While working on other issues related to WORD indexes I realized something that seems like needing further investigation.
I am not exactly sure if the following is true but the current conversion might decide that the word index is responsible for driving a particular query. In this case the generated code would look like this:
new FindQuery(ttMiddel, "upper(tt0.extField[0]) = 'MATCH-PHRASE'", null, "tt0.extField asc").first());
Note that, since the
tt0
has a word index with ext-field
as component, the sort parameter seems normal.
The problem is not the fact that we ignore the index in FWD, but the fact that we cannot generate a valid ORDER
clause in the SQL query. It will be something like
ORDER BY tt0.extField ASC
The problem is
extField
is an extent property and will be found in tt0__5
not in tt0
table. As result the SQL server will return an error. Let's hope this is not the case.