| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: AW: Inserting a select statement result into another ta ble |
| Date: | 2000-10-13 09:07:22 |
| Message-ID: | 200010130907.FAA23042@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ Charset ISO-8859-1 unsupported, converting... ]
>
> > > > He does ask a legitimate question though. If you are
> > going to have a
> > > > LIMIT feature (which of course is not pure SQL), there
> > seems no reason
> > > > you shouldn't be able to insert the result into a table.
> > >
> > >
> >
> > This is an interesting idea. We don't allow ORDER BY in
> > INSERT INTO ...
> > SELECT because it doesn't make any sense, but it does make sense if
> > LIMIT is used:
>
> An "order by" also makes sense if you want to create a presorted table
> for faster access. I don't see why we should disallow it.
Like CLUSTER. I see.
--
Bruce Momjian | http://candle.pha.pa.us
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 | Martin A. Marques | 2000-10-13 11:02:50 | RE: backup and restore |
| Previous Message | Bruce Momjian | 2000-10-13 09:07:01 | Re: AW: AW: ALTER TABLE DROP COLUMN |