From: Denis Zaitsev <zzz@cd-club.ru>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@postgresql.org
Subject: Re: Are scalar type's in/out functions implicitly STRICT?
Date: Sun, 2 Mar 2003 05:40:33 +0500
Message-ID: <20030302054033.A30850@natasha.zzz.zzz> (raw)
In-Reply-To: <1341.1046400277@sss.pgh.pa.us>
References: <20030228054544.A4208@natasha.zzz.zzz>
<1341.1046400277@sss.pgh.pa.us>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: zzz@cd-club.ru, tgl@sss.pgh.pa.us
Subject: Re: Are scalar type's in/out functions implicitly STRICT?
In-Reply-To: <20030302054033.A30850@natasha.zzz.zzz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox