Received: from tech.com.au (IDENT:root@techpt.lnk.telstra.net [139.130.75.122]) by hub.org (8.9.3/8.9.3) with ESMTP id FAA70945; Thu, 3 Feb 2000 05:49:07 -0500 (EST) (envelope-from chris@bitmead.com) Received: from bitmead.com (tardis [203.41.180.243]) by tech.com.au (8.9.3/8.9.3) with ESMTP id VAA29627; Thu, 3 Feb 2000 21:46:45 +1100 Sender: chris@tech.com.au Message-ID: <38995C95.38897035@bitmead.com> Date: Thu, 03 Feb 2000 21:46:45 +1100 From: Chris X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i686) X-Accept-Language: en MIME-Version: 1.0 To: Hannu Krosing CC: Tom Lane , pgsql-hackers@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL References: <3898DA32.793A98BA@nimrod.itg.telecom.com.au> <24649.949546519@sss.pgh.pa.us> <3898F8DE.8159BFE7@nimrod.itg.telecom.com.au> <389958FB.2E6927B5@tm.ee> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hannu Krosing wrote: > Maybe SELECT ** FROM BASE would be more flexible as it leaves the standard > SQL with its "standard" meaning ? That was my first thought and it's definitely a possibility. My argument against it is that SQL doesn't have a "standard meaning" in the case of inheritance, and ** is an incompatibility with OQL. I suspect we need both. Something like SET GET_INHERITED_COLUMNS true; etc. > We will have to change the API sometime not too distant anyway, the current > api is unable to deal with anything that does not have a nice textual > representation (like an image or sound) in spite of all the talks about > easy extensibility - the extensibility is all in the backend, ther is no > easy way to get new datatypes in/out. What about PQbinaryTuples() and friends?