I would be convenient if you could say "x INCLUDE y" or something like that and the engine would figure out the join by foreign/primary keys.
Might seem like a small improvement, but if you write lots of queries it would be a significant time saver.
Might seem like a small improvement, but if you write lots of queries it would be a significant time saver.
x JOIN y
Postgres automatically uses same-name columns for the join. So in the example I gave you, actually "ON x.id=y.id" is redundant. I just added it because if I hadn't someone else would've replied "oh but that only works if you name the columns the same name"
Also, in any less than trivial scenario you will have to think how to handle the edge cases. But again, that's a property of the operation, not of the language.