I replied before.
I still know next to nothing about SQL instructions.
I know that if you design your tables well, you don't need complicated JOIN stuff.
I jump straight to the right index, most of times, anyways.
You are viewing a single comment's thread from:
I'm asking, because (at least in theory) in Postgres JOIN condition can be any expression yielding boolean. I haven't used any other expression that =.
Posted via D.Buzz
So... I guess you mean something other than a single condition (comparison) that returns a true/false statement.
Perhaps an OR condition?
Never had to use that, but I could imagine that being very useful stuff for data-analysis. At which point speed might not be your first concern, meaning you might as well solve that in code...
It's really hard to reply to a DB question without an actual use-case and data.
Generally, I'd leave logic operations to the language you are developing in.
The rest of the logic should be covered by designing the tables well.
No, I mean something like
JOIN ON a > b
or
JOIN ON a <> b
Posted via D.Buzz