> therefore that whole WHERE clause doesn't exist either
replyNo, therefore the condition is unsatisfiable and equivalent to WHERE FALSE. And that's letting you ignore the SQL spec, which says the query is invalid and should return "Column not found" because the column name cannot be resolved.
> We're comparing 4 and 5. Precedent?
I really hope you're trolling, for your own sake.
The explanation is more damning than the devex.
replyThe condition is unsatisfiable, and the engine went ahead and gave a 0-warning result?
Are you claiming that 4 = 5?
replyI'm claiming that
reply1) It would be no more fucked up than anything else that has been grandfathered into our tools.
2) If it already had mass adoption in the market, people would jump onto this thread to explain to me that I just don't understand the brilliant semantics behind language of why 4 = 5.
Apologist for what?
reply