Received: from mailo.vtcif.telstra.com.au (mailo.vtcif.telstra.com.au [202.12.144.17]) by hub.org (8.9.3/8.9.3) with ESMTP id WAA45114; Wed, 2 Feb 2000 22:52:18 -0500 (EST) (envelope-from chrisb@nimrod.itg.telstra.com.au) Received: (from uucp@localhost) by mailo.vtcif.telstra.com.au (8.8.2/8.6.9) id OAA26467; Thu, 3 Feb 2000 14:51:46 +1100 (EST) Received: from maili.vtcif.telstra.com.au(202.12.142.17) via SMTP by mailo.vtcif.telstra.com.au, id smtpdTnls1_; Thu Feb 3 14:51:17 2000 Received: (from uucp@localhost) by maili.vtcif.telstra.com.au (8.8.2/8.6.9) id OAA04731; Thu, 3 Feb 2000 14:51:16 +1100 (EST) Received: from localhost(127.0.0.1), claiming to be "mail.cdn.telstra.com.au" via SMTP by localhost, id smtpd0j5jgw; Thu Feb 3 14:50:16 2000 Received: from lunitari.nimrod.itg.telecom.com.au (lunitari.nimrod.itg.telecom.com.au [192.53.254.48]) by mail.cdn.telstra.com.au (8.8.2/8.6.9) with ESMTP id OAA06218; Thu, 3 Feb 2000 14:50:12 +1100 (EST) Received: from nimrod.itg.telecom.com.au (majere [192.53.254.45]) by lunitari.nimrod.itg.telecom.com.au (8.9.1/8.9.3) with ESMTP id OAA10470; Thu, 3 Feb 2000 14:49:32 +1100 (EST) Sender: chrisb@nimrod.itg.telstra.com.au Message-ID: <3898FA9E.22D33715@nimrod.itg.telecom.com.au> Date: Thu, 03 Feb 2000 14:48:46 +1100 From: Chris Bitmead Reply-To: chris@bitmead.com Organization: IBM Global Services X-Mailer: Mozilla 4.6 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Momjian CC: chris@bitmead.com, "pgsql-hackers@postgreSQL.org" , pgsql-sql@postgresql.org, pgsql-general@postgresql.org Subject: Re: [GENERAL] Proposed Changes to PostgreSQL References: <200002030257.VAA00457@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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).