From: | "Dean Gibson (DB Administrator)" <postgresql4(at)ultimeth(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: Is NULLIF nullable? |
Date: | 2004-11-10 05:12:43 |
Message-ID: | 5.1.0.14.2.20041109211131.00a89d00@imaps.mailpen.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
You can ignore my question below, since I just put the field definition
below in an SQL FUNCTION and marked it STRICT.
-- Dean
Dean Gibson (DB Administrator) wrote on 2004-11-09 19:29:
>Recently I asked about why a field from the nullable side of an OUTER JOIN
>was causing the JOIN to be inefficient, and was told that it was because
>that field had a CASE statement as part of its definition, and that CASE
>(and by extension COALESCE) were non-nullable constructs.
>
>Is NULLIF nullable, in that sense?
>
>Reason: I'd like to define a VIEW with a field definition thusly:
>
>'P.O. Box' || NULLIF( po_box, ' '::char ) AS ...
>
>And I would like the field thusly defined to be nullable.
>
>-- Dean
From | Date | Subject | |
---|---|---|---|
Next Message | sad | 2004-11-10 06:23:02 | Re: A transaction in transaction? Possible? |
Previous Message | Dean Gibson (DB Administrator) | 2004-11-10 03:29:49 | Is NULLIF nullable? |