Re: Are scalar type's in/out functions implicitly STRICT? - Mailing list pgsql-sql

From Denis Zaitsev
Subject Re: Are scalar type's in/out functions implicitly STRICT?
Date
Msg-id 20030302054033.A30850@natasha.zzz.zzz
Whole thread Raw
In response to Re: Are scalar type's in/out functions implicitly STRICT?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-sql
On Thu, Feb 27, 2003 at 09:44:37PM -0500, Tom Lane wrote:
> Denis Zaitsev <zzz@cd-club.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.


pgsql-sql by date:

Previous
From: "Nicolas Fertig"
Date:
Subject: OUTER JOIN with filter
Next
From: Denis Zaitsev
Date:
Subject: Re: Are scalar type's in/out functions implicitly STRICT?