From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Don Baccus <dhogaza(at)pacifier(dot)com> |
Cc: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'PostgreSQL-development'" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] column aliases |
Date: | 2000-01-24 19:29:29 |
Message-ID: | 200001241929.OAA07794@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> At 12:00 PM 1/24/00 +0100, Zeugswetter Andreas SB wrote:
>
> >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;
>
> Yeah...in porting the arsDigita Community System over from
> Oracle, we created a dummy table called "dual" because of
> the clunky Oracle-ism involving that table.
>
> In other words, in Oracle you can't say:
>
> select sydate();
>
> because you must have a "from" clause. By convention you
> use a dummy built-in table called "dual" which has one row:
>
> select sysdate() from dual;
>
> Ugh. I agree that being able to exclude the from clause
> altogether is nice.
Yes, with INFORMIX, we use 'tab1' as a one-row table.
The cool part is SELECT pg_class.* is the same as SELECT * FROM
pg_class.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Don Baccus | 2000-01-24 19:35:37 | Re: [HACKERS] Well, then you keep your darn columns |
Previous Message | Bruce Momjian | 2000-01-24 19:25:34 | Re: [HACKERS] Well, then you keep your darn columns |