From: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
---|---|
To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
Cc: | "'chris(at)bitmead(dot)com'" <chris(at)bitmead(dot)com>, "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: AW: [HACKERS] Proposed Changes to PostgreSQL |
Date: | 2000-02-03 22:48:04 |
Message-ID: | 389A05A4.566417B4@nimrod.itg.telecom.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Zeugswetter Andreas SB wrote:
> > Also there should be an settable option that specifies that "*" should
> > also return the normally ignored columns of oid and classname. This is
> > so that OO programs that embed SQL into them also get back the oid and
> > classname which are required for the behind the scenes implementation
> > of an ODMG client. Something like...
>
> why don't they simply always
> select oid, classname, * from ...
> The reason I suggest this is, because implementing joins to return the
> correct oid, classname seems very complex.
Because I envisage people using an ODBMS-ish interface and allowing
use of SQL queries. This infrastructure wouldn't work without oid and
classname. Forcing always to add oid, classname would be
repetitive and error prone.
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 2000-02-03 22:53:33 | Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL |
Previous Message | Chris Bitmead | 2000-02-03 22:43:48 | Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL |