X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D43A8476858 for ; Sat, 1 Mar 2003 21:03:49 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 20483-10 for ; Sat, 1 Mar 2003 21:03:42 -0500 (EST) Received: from zzz.zzz (unknown [212.57.173.125]) by postgresql.org (Postfix) with ESMTP id D8F83476000 for ; Sat, 1 Mar 2003 19:46:34 -0500 (EST) Date: Sun, 2 Mar 2003 05:41:47 +0500 From: Denis Zaitsev To: pgsql-sql@postgresql.org Subject: Re: Are scalar type's in/out functions implicitly STRICT? Message-ID: <20030302054147.B30850@natasha.zzz.zzz> References: <20030228054544.A4208@natasha.zzz.zzz> <20030228032444.GA4648@wolff.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030228032444.GA4648@wolff.to>; from bruno@wolff.to on Thu, Feb 27, 2003 at 09:24:44PM -0600 X-Virus-Scanned: by amavisd-new X-Archive-Number: 200303/21 X-Sequence-Number: 12061 On Thu, Feb 27, 2003 at 09:24:44PM -0600, Bruno Wolff III wrote: > 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? Yes, I am - v1. > The version zero method doesn't have a way handle nulls other than by > declaring the function strict. > Hmm, examples/docs show such a way for v0...