I think about my self as quite SQL-savvy person, I used to optimize quite complex queries and is able to read plans for Oracle, Postgres and MySQL.<p>And yet, I've got not idea why would anybody need right join.<p>Have you guys ever had a case when you'd need a right join? I've been to the field for 15 years and yet to see people using right join in the wild.<p>Like the last example in this link - why would you do that? Most probably your business logic focuses on dogs, something like "find dogs with no owner" or something, In this case it is much more readable and straight forward to go with left join or even with sub-select where you'd have something like 'select * from dogs where owner_id not in (select id from owners)'.<p>Have you used right joins and if you have can you explain the use case?
I really feel like we need a lower level expression language than SQL, one based on actual query plans rather than a declarative thing.<p>Having that, and helping people learn that, would make it much harder to not “get” how joins and the like end up working
Does SQL Join allow equality with operators like ilike, like,... or custom equality function ?<p>select * from a
inner join b
on mycustomfunction(a, b);