| From: | Denis Zaitsev <zzz(at)cd-club(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Are scalar type's in/out functions implicitly STRICT? |
| Date: | 2003-03-02 00:40:33 |
| Message-ID: | 20030302054033.A30850@natasha.zzz.zzz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Thu, Feb 27, 2003 at 09:44:37PM -0500, Tom Lane wrote:
> Denis Zaitsev <zzz(at)cd-club(dot)ru> writes:
> > So, I create some new scalar type and I don't declare its in/out
> > functions as STRICT. But PostgreSQL copes with them such as they
> > would be STRICT - they never get the NULL value.
>
> This is likely true in many places --- for example, COPY has a shortcut
> because it wants to substitute \N for nulls. It would not be a bright
> idea to assume that it's true in every place and forevermore. In
> general, if you have a C function and don't want to be bothered with
> explicit PG_ISNULL testing, you'd better mark it STRICT.
>
Ok, thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Denis Zaitsev | 2003-03-02 00:41:47 | Re: Are scalar type's in/out functions implicitly STRICT? |
| Previous Message | Bruno Wolff III | 2003-03-02 00:23:48 | Re: Beginner needs help |