| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin Clift <jc(at)telstra(dot)net> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LinuxTag wrapup |
| Date: | 2004-07-05 02:57:42 |
| Message-ID: | 17410.1088996262@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Clift <jc(at)telstra(dot)net> writes:
> There's also their "FROM DUAL" workaround (in common usage) as well.
[ yawn... ]
regression=# create table dual();
CREATE TABLE
regression=# insert into dual default values;
INSERT 292940 1
regression=# select 2+2 from dual;
?column?
----------
4
(1 row)
Anyone who needs this has always been able to make it trivially
(though you once had to invent a random column name for the one
required column).
Does anyone have the foggiest idea why they named it DUAL? Doesn't
seem a very mnemonic choice to me...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2004-07-05 02:58:13 | Re: Nested Transactions, Abort All |
| Previous Message | Justin Clift | 2004-07-05 02:52:46 | Re: Adding column comment to information_schema.columns |