D
dlauzon
Guest
I see two types of sorting: the one that comes with following a given index for record selection and the one that gives the order in which we want to process records. The idea would be to have a keyword to "force" a Client Sort, e.g. we could have a USE-INDEX for query performance, but have "client sort BY clauses" for the processing order once the result list is built or not have a USE-INDEX, but want the query to use the best available index based on field selection, and not on "client sort BY clauses". Currently, we have to use an additional temp-table to do something like that, but the AVM already provides a Client Sorting mechanism that we could tap into. And often, developers don't understand how indexes are used and don't use an additional temp-table, so this result in poor performance and/or extra records reads. The idea would, in bonus, prevent some of this.
Continue reading...
Continue reading...