X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 472E4475956 for ; Thu, 27 Feb 2003 22:44:39 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 60363-07 for ; Thu, 27 Feb 2003 22:44:28 -0500 (EST) Received: from wolff.to (wolff.to [66.93.249.74]) by postgresql.org (Postfix) with SMTP id 76602474E42 for ; Thu, 27 Feb 2003 22:11:01 -0500 (EST) Received: (qmail 4662 invoked by uid 500); 28 Feb 2003 03:24:44 -0000 Date: Thu, 27 Feb 2003 21:24:44 -0600 From: Bruno Wolff III To: Denis Zaitsev Cc: pgsql-sql@postgresql.org Subject: Re: Are scalar type's in/out functions implicitly STRICT? Message-ID: <20030228032444.GA4648@wolff.to> Mail-Followup-To: Denis Zaitsev , pgsql-sql@postgresql.org References: <20030228054544.A4208@natasha.zzz.zzz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030228054544.A4208@natasha.zzz.zzz> User-Agent: Mutt/1.3.25i X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/609 X-Sequence-Number: 12007 On Fri, Feb 28, 2003 at 05:45:44 +0500, Denis Zaitsev wrote: > 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. And this is not > documented, AFAIK. Have I missed something or is it a some hard > well-known etc. fact? Thanks in advance. Are you using the version one calling sequence? The version zero method doesn't have a way handle nulls other than by declaring the function strict.