MUtil SelectModel drops sort columns silently if it is not sure the column exists.
This behaviour should be changed so that if a column is named in a sort statement, that column should be supposed to exist. Then if the code tries to sort on a non-existing column the model will generate an SQL error during execution - which means we know there is something wring in the code - while as long as column exists it will always be used for a sort.
MUtil SelectModel drops sort columns silently if it is not sure the column exists.
This behaviour should be changed so that if a column is named in a sort statement, that column should be supposed to exist. Then if the code tries to sort on a non-existing column the model will generate an SQL error during execution - which means we know there is something wring in the code - while as long as column exists it will always be used for a sort.