pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Hannu Krosing <hannu@tm.ee>
To: Chris <chris@bitmead.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Date: Fri, 04 Feb 2000 00:38:28 +0200
Message-ID: <389A0364.A1E6E766@tm.ee> (raw)
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>
	<38995C95.38897035@bitmead.com>

Chris wrote:
> 
> 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?

They don't help you at all when doing inserts and are by definition in native
byte order on queries.

Something like [ PREPARE query; BIND arguments ; EXEC ] which knows about
binary 
formats would be needed here.

One could use LOs except that the current ineffective implementation.

-------------
Hannu



view thread (68+ messages)  latest in thread

Message-ID: <389A0364.A1E6E766@tm.ee>
Permalink:  ../389A0364.A1E6E766@tm.ee/
Also on:    postgresql.org/message-id/389A0364.A1E6E766@tm.ee

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: hannu@tm.ee, chris@bitmead.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org
  Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
  In-Reply-To: <389A0364.A1E6E766@tm.ee>
  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> <38995C95.38897035@bitmead.com> <389A0364.A1E6E766@tm.ee>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox