Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f170hEx63365 for ; Tue, 6 Feb 2001 19:43:14 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f170hA926604; Tue, 6 Feb 2001 19:43:10 -0500 (EST) To: Florent Guillaume cc: pgsql-hackers@postgresql.org, pgman@candle.pha.pa.us Subject: Re: Re: [SQL] PL/PGSQL function with parameters In-reply-to: <20010206221522.A21727@twin.efge.org> References: <7F124BC48D56D411812500D0B747251480F3D4@FILESERVER002> <7F124BC48D56D411812500D0B747251480F3D4@FILESERVER002> <20010206221522.A21727@twin.efge.org> Comments: In-reply-to Florent Guillaume message dated "Tue, 06 Feb 2001 22:15:22 +0100" Date: Tue, 06 Feb 2001 19:43:10 -0500 Message-ID: <26601.981506590@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/209 X-Sequence-Number: 4340 Florent Guillaume writes: > On this same subject, the plpgsql doc says to use > SELECT expression INTO var FROM ... > but Bruce's book, in several examples ("PL/PGSQL Functions" for instance, > node203.html) uses > SELECT INTO var expression FROM ... > Both should work, but there may be there's something to straighten up here. IIRC, the plpgsql code is actually *very* lax about where you put the INTO; it'll suck it out from almost anyplace in the query string ... regards, tom lane