Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id XAA50948; Wed, 2 Feb 2000 23:03:28 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id XAA03857; Wed, 2 Feb 2000 23:03:14 -0500 (EST) From: Bruce Momjian Message-Id: <200002030403.XAA03857@candle.pha.pa.us> Subject: Re: [GENERAL] Proposed Changes to PostgreSQL In-Reply-To: <3898FA9E.22D33715@nimrod.itg.telecom.com.au> from Chris Bitmead at "Feb 3, 2000 02:48:46 pm" To: chris@bitmead.com Date: Wed, 2 Feb 2000 23:03:14 -0500 (EST) CC: "pgsql-hackers@postgreSQL.org" , pgsql-sql@postgreSQL.org, pgsql-general@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit I can live with this. Thanks. > Bruce Momjian wrote: > > > > I already have a patch for this one. The change is a few pretty simple > > > changes > > > to gram.y. > > > > OK, you will have to canvas the general list to make sure this does not > > break things for people, though our inheritance system needs an overhaul > > badly. > > This is already CCed to the general list. > > > I fear it is totally against the way our API works. How does someone > > see how many columns in the returned row? > > A new API PQnfieldsv(PQresult, tupnum) or some such. > > > Yikes. Strange. > > Strange for C code perhaps. Very useful for constructing real objects in > OO application code framework. > > > Can we just return nulls for the empty fields? > > Well, I think we should probably distinguish between a field that is > null, > and a field that simply doesn't exist. > > > How many new API calls are required? > > Perhaps just the one. (above). > -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026