Why are CASE-expressions in the list documenting operator precedence?

In the list here:


case-expressions are put at the same precedence level as BETWEEN, between the NOT operator and the comparison operators.

However, case-expressions always begin with CASE and end with END, and all subexpressions are also delimited by the CASE keywords. They’re like parenthetical expressions, so I don’t understand why case-expressions are on this list.

Is there an SQL expression that would be parsed differently if the case-expression precedence was set higher or lower?

Go to Source
Author: JoL