Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46] (may be forged)) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2KIYEN60957 for ; Tue, 20 Mar 2001 13:34:14 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id NAA06604; Tue, 20 Mar 2001 13:32:49 -0500 (EST) From: Bruce Momjian Message-Id: <200103201832.NAA06604@candle.pha.pa.us> Subject: Re: Re: [GENERAL] Re: temp table creation In-Reply-To: "from Peter Eisentraut at Mar 20, 2001 07:02:22 pm" To: Peter Eisentraut Date: Tue, 20 Mar 2001 13:32:49 -0500 (EST) CC: Tom Lane , Alfonso Peniche , PostgreSQL-documentation X-Mailer: ELM [version 2.4ME+ PL77 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200103/109 X-Sequence-Number: 543 > Tom Lane writes: > > > the spec contemplates INTO as introducing a list of scalar variables to > > be assigned to. plpgsql and ecpg both use this meaning for SELECT INTO. > > > > Would anyone object if I add text to the SELECT INTO ref page that > > points this out, and recommends CREATE TABLE AS as the preferred > > syntax? > > I agree. SELECT INTO is misnamed; it sounds like INSERT ... SELECT. Yes. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026