Document effect of constant folding on CASE.
Back-patch to all supported versions. Laurenz Albe
This commit is contained in:
parent
5f538ad004
commit
d53f7cf116
|
@ -10563,6 +10563,16 @@ SELECT a,
|
||||||
SELECT ... WHERE CASE WHEN x <> 0 THEN y/x > 1.5 ELSE false END;
|
SELECT ... WHERE CASE WHEN x <> 0 THEN y/x > 1.5 ELSE false END;
|
||||||
</programlisting>
|
</programlisting>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<note>
|
||||||
|
<para>
|
||||||
|
As described in <xref linkend="xfunc-volatility">, functions and
|
||||||
|
operators marked <literal>IMMUTABLE</literal> can be evaluated when
|
||||||
|
the query is planned rather than when it is executed. This means
|
||||||
|
that constant parts of a subexpression that is not evaluated during
|
||||||
|
query execution might still be evaluated during query planning.
|
||||||
|
</para>
|
||||||
|
</note>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 id="functions-coalesce-nvl-ifnull">
|
<sect2 id="functions-coalesce-nvl-ifnull">
|
||||||
|
|
Loading…
Reference in New Issue