diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2011-06-04 23:12:27 +0300 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2011-06-04 23:13:28 +0300 |
| commit | 39dbc62adedc8758580d099e4a21f1e5a4a0bf85 (patch) | |
| tree | 047621ac749c88d882910ded568b3ecb181dc47c | |
| parent | ec688fd346e7f3413bd69ff2413a1e6da6aec402 (diff) | |
Fix documentation reference to "above" example
found by Thom Brown
| -rw-r--r-- | doc/src/sgml/plpython.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml index daefc583f3b..f1798acc71b 100644 --- a/doc/src/sgml/plpython.sgml +++ b/doc/src/sgml/plpython.sgml @@ -410,7 +410,8 @@ $$ LANGUAGE plpythonu; If an SQL null value<indexterm><primary>null value</primary><secondary sortas="PL/Python">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, |
