I think an advanced SQL user would probably notice that the entire problem here is caused by an incorrectly normalized schema. An order has to be placed by a customer, which is usually a type of person, but sometimes the customer person has a status of staff member, which in the example usecase was denormalized into a different table, resulting in the naturally inefficient access pattern.