summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane2007-10-30 19:06:56 +0000
committerTom Lane2007-10-30 19:06:56 +0000
commit897313e824f6190937e7d005845021e2b1197668 (patch)
treed6ddb246d8d54c57b1a8b06af970bc27e2a90923
parentb973530737805710e67730393000b3786d454292 (diff)
Add a note pointing out that some other databases make GREATEST and
LEAST handle NULL arguments differently than we do. Per a discussion on 30-Jun that somehow didn't get done.
-rw-r--r--doc/src/sgml/func.sgml6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
index 5feb572de2d..34e9d56e659 100644
--- a/doc/src/sgml/func.sgml
+++ b/doc/src/sgml/func.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.405 2007/10/25 18:54:03 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/func.sgml,v 1.406 2007/10/30 19:06:56 tgl Exp $ -->
<chapter id="functions">
<title>Functions and Operators</title>
@@ -9016,7 +9016,9 @@ SELECT NULLIF(value, '(none)') ...
<para>
Note that <function>GREATEST</> and <function>LEAST</> are not in
- the SQL standard, but are a common extension.
+ the SQL standard, but are a common extension. Some other databases
+ make them return NULL if any argument is NULL, rather than only when
+ all are NULL.
</para>
</sect2>
</sect1>