Re: [HACKERS] column aliases

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'PostgreSQL-development'" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] column aliases
Date: 2000-01-24 11:00:08
Message-ID: 219F68D65015D011A8E000006F8590C603FDC216@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> >What it looks like to me is that we have a bug in the
> expansion of '*'.
> >It should be generating columns for both the explicit and
> the implicit
> >FROM clause, but it's evidently deciding that it should only produce
> >output columns for the first one.
>
> Yes, since it is joining the two tables it should be returning all
> columns of the join.
>
> >This may go a long way towards explaining why people have been so
> >readily confused by the implicit-FROM-clause business!
>
> It *is* confusing, that's for sure!

IMHO, if there exists a from clause, we could insist,
that all tables are listed (no implicitly added table),
since it is really too error prone.

What I would not like to see removed is the ability to
avoid the from clause alltogether. Like in:

select xor.eval;

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Robinson 2000-01-24 11:12:46 fatal copy in/out error (6.5.3)
Previous Message Zeugswetter Andreas SB 2000-01-24 10:53:45 AW: [HACKERS] Implementing STDDEV and VARIANCE