X-Original-To: pgsql-sql@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C10ED475F32 for ; Thu, 27 Feb 2003 21:24:14 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 41609-10 for ; Thu, 27 Feb 2003 21:24:03 -0500 (EST) Received: from zzz.zzz (unknown [212.57.173.80]) by postgresql.org (Postfix) with ESMTP id 3615E4763FB for ; Thu, 27 Feb 2003 19:56:28 -0500 (EST) Date: Fri, 28 Feb 2003 05:45:44 +0500 From: Denis Zaitsev To: pgsql-sql@postgresql.org Subject: Are scalar type's in/out functions implicitly STRICT? Message-ID: <20030228054544.A4208@natasha.zzz.zzz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/607 X-Sequence-Number: 12005 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.