Add note that COALESCE and NULLIF are shorthand forms of CASE.

diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 5b3012625ea2a4d101dc27c6a9140ecf6099781d..48bdb2a5e1cf19014f0819d25b3f22b6b8387b30 100644 (file)
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.41 2000/12/14 22:30:56 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/func.sgml,v 1.42 2000/12/16 18:33:13 tgl Exp $ -->
 
 <chapter id="functions">
  <title>Functions and Operators</title>
@@ -2618,6 +2618,19 @@ SELECT COALESCE(description, short_description, '(none)') ...
 SELECT NULLIF(value, '(none)') ...
 </programlisting>
   </para>
+
+  <tip>
+   <para>
+    <function>COALESCE</function> and <function>NULLIF</function> are
+    just shorthand for <token>CASE</token> expressions.  They are actually
+    converted into <token>CASE</token> expressions at a very early stage
+    of processing, and subsequent processing thinks it is dealing with
+    <token>CASE</token>.  Thus an incorrect <function>COALESCE</function> or
+    <function>NULLIF</function> usage may draw an error message that
+    refers to <token>CASE</token>.
+   </para>
+  </tip>
+
  </sect1>