Currently, when a select result is converted into objects, it is assumed that the selected columns are all columns in the table and that they are in the order as in the schema xml. This beraks if the user starts to add select rows in the criteria.
Currently one must implement a custom record mapper to deal with this situation.
It would be a nice feature if the record mapper could inspect the select crititera and map the columns accordingly. An appropriate error should be thrown if the record mapper does not map the result set.
|API Change for Record mapper interface||Closed||Unassigned|