X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 9A1609DC86A for ; Mon, 30 Jan 2006 18:11:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 86691-08 for ; Mon, 30 Jan 2006 18:11:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 717CA9DC855 for ; Mon, 30 Jan 2006 18:11:53 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0UMBsus024079; Mon, 30 Jan 2006 17:11:54 -0500 (EST) To: Richard Jones cc: pgsql-interfaces@postgresql.org Subject: Re: Find out if a parameter/return field is NULLABLE using Describe In-reply-to: <20060130203822.GA16111@furbychan.cocan.org> References: <20060130203822.GA16111@furbychan.cocan.org> Comments: In-reply-to Richard Jones message dated "Mon, 30 Jan 2006 20:38:22 +0000" Date: Mon, 30 Jan 2006 17:11:54 -0500 Message-ID: <24078.1138659114@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.101 required=5 tests=[AWL=0.101] X-Spam-Score: 0.101 X-Spam-Level: X-Archive-Number: 200601/45 X-Sequence-Number: 5961 Richard Jones writes: > It doesn't seem to be possible to find out if a parameter or result > field is nullable using the Describe protocol. This isn't something that the backend tracks at all, so changing the wire protocol would be the least of your problems in making it happen... regards, tom lane