AW: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Hannu Krosing'" <hannu(at)tm(dot)ee>, "'chris(at)bitmead(dot)com'" <chris(at)bitmead(dot)com>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>, "'pgsql-sql(at)postgresql(dot)org'" <pgsql-sql(at)postgresql(dot)org>
Subject: AW: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Date: 2000-02-03 15:21:03
Message-ID: 219F68D65015D011A8E000006F8590C603FDC239@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-sql


> > > > I would propose that that anytime you do a SELECT *
> from a base table
> > > > that you would get back the full rows from those sub tables.
>
> Maybe SELECT ** FROM BASE would be more flexible as it leaves
> the standard
> SQL with its "standard" meaning ?

I like the idea of not messing with the traditional meaning of the *.
The Informix select * from table_with_subclasses also only returns
the parent columns.

Of course I would also like that the default select * from table
return all subclass rows.

Imho there is no real argument against extra syntax to select
all columns of subclasses though.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2000-02-03 15:30:32 AW: [HACKERS] SELECT FOR UPDATE leaks relation refcounts
Previous Message Oliver Elphick 2000-02-03 15:06:42 Re: [HACKERS] Recent RI changes have broken something

Browse pgsql-sql by date

  From Date Subject
Next Message Mark Volpe 2000-02-03 15:21:44 Re: [SQL] Question about SELECT and ORDER BY
Previous Message Vladimir Terziev 2000-02-03 14:34:31 Question about SELECT and ORDER BY