Hi Team,
We are facing an issue when we try to fetch the data through a query entity with a specified column sorting. When we execute the expression we specify the column on which sorting needs to happen. But when we get the result back we see two sorting columns in the result set.
Is there any reason that might cause this? This is causing us perfomance issues
Discussion posts and replies are publicly visible
Hello,
We observed a similar behavior in our project. On a table with a large number of rows (20,000,000 rows), performing a multi-column sort including the primary key caused the index that was supposed to be used to be considered irrelevant by the DBMS (Oracle). We had to create a composite index, including the desired column and the primary key, in order for it to be used.