From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Unclear documentation |
Date: | 2005-11-10 03:30:10 |
Message-ID: | 4372BEC2.7070304@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In the CREATE FUNCTION docs I notice this:
RETURNS NULL ON NULL INPUT or STRICT indicates that the function always
returns null whenever any of its arguments are null. If this parameter
is specified, the function is not executed when there are null
arguments; instead a null result is assumed automatically.
I'm wondering what this means when the function returns a composite
type, or a setof scalar or a setof composite?
So if you indicate STRICT, does PostgreSQL assume one row of all nulls
for each column in the return composite type? Perhaps someone who knows
better could tweak the docs a bit?
Cheers,
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2005-11-10 03:46:21 | Re: Comments from a Firebird user via Borland Newsgroups. |
Previous Message | Christopher Kings-Lynne | 2005-11-10 02:36:51 | Re: [COMMITTERS] dbsamples - dbsamples: Imported Sources |