Views creates certain JOINs behind the scenes, e.g. for fields or filders added via the UI.
I have a view with such an implicit join based on an entityreference field. In order to get the desired results I need this join to be the first one, but Views happens to place it as the last JOIN (other joins in the query come from other fields and Views relationships).
Can I change the order of the joins, while keeping all fields and filters configured via the Views UI?
As a workaround I can explicitly add a relationship based on the entityreference field in question and order it as the first one. This works, but it adds an extra join that I don't need, which has a performance impact.