Hello,
I noticed a regression introduced with this change.
If we search on a domain such as the UNION is triggered, with a sort on a Reference field of the main table, the query fails. This is because __searched_column
ignores Reference fields (because they are lazy-loaded by default).
This was not a problem before because even though the column was not in the searched columns, it always existed on the table, so a sort on the column did not cause any issue.
This is not specific to Reference fields, but may happen as soon as a search on a domain that triggers the UNION sorts on a lazy-loaded field.
History | |||
---|---|---|---|
Date | User | Action | Args |
2021-09-24 13:55:15 | ced | unlink | issue10658 messages |
2021-09-24 12:23:45 | jcavallo | set | messageid: <1632479025.987471.PFKFJCG2J5NY6RLP.issue10658@tryton.org> |
2021-09-24 12:23:45 | jcavallo | set | recipients: + ced, nicoe, albertca, roundup-bot, reviewbot |
2021-09-24 12:23:45 | jcavallo | link | issue10658 messages |
2021-09-24 12:23:45 | jcavallo | create |
Showing 10 items. Show all history (warning: this could be VERY long)