aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2011-06-04 23:12:27 +0300
committerPeter Eisentraut <peter_e@gmx.net>2011-06-04 23:12:27 +0300
commit36a1ba9d5e25d74fb50dfaccefe86f406f337a74 (patch)
treebb95a46acf453e6dfd3849e0f16d17474c2cb9d9 /doc/src
parent4dd4bd4d8e1314b0c242e468d084400bf0734202 (diff)
downloadpostgresql-36a1ba9d5e25d74fb50dfaccefe86f406f337a74.tar.gz
postgresql-36a1ba9d5e25d74fb50dfaccefe86f406f337a74.zip
Fix documentation reference to "above" example
found by Thom Brown
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/plpython.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index ffc1d3ab3db..eda2bbf34c5 100644
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -400,7 +400,8 @@ $$ LANGUAGE plpythonu;
If an SQL null value<indexterm><primary>null value</primary><secondary
sortas="PL/Python">in PL/Python</secondary></indexterm> is passed to a
function, the argument value will appear as <symbol>None</symbol> in
- Python. The above function definition will return the wrong answer for null
+ Python. For example, the function definition of <function>pymax</function>
+ shown in <xref linkend="plpython-funcs"> will return the wrong answer for null
inputs. We could add <literal>STRICT</literal> to the function definition
to make <productname>PostgreSQL</productname> do something more reasonable:
if a null value is passed, the function will not be called at all,