Message-ID: <44A2C0EF.3@presinet.com>
Date: Wed, 28 Jun 2006 10:48:31 -0700
From: Bricklen Anderson <banderson@presinet.com>
User-Agent: Thunderbird 1.5.0.4 (X11/20060615)
MIME-Version: 1.0
To: KeithW@narrowpathinc.com
Cc: PostgreSQL SQL <pgsql-sql@postgresql.org>
Subject: Re: "CASE" is not a variable
References: <20060628154728.M33440@narrowpathinc.com>
	<21800.1151511389@sss.pgh.pa.us>
	<20060628173010.M51266@narrowpathinc.com>
In-Reply-To: <20060628173010.M51266@narrowpathinc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Keith Worthington wrote:
>>> "Keith Worthington" <keithw@narrowpathinc.com> writes:
>>> The following is a section of code inside an SQL function.
>> On Wed, 28 Jun 2006 12:16:29 -0400, Tom Lane wrote
>> SQL, or plpgsql?  It looks to me like misuse of the plpgsql INTO clause
>> (there can be only one).
>>
>> 			regards, tom lane
> 
> plpgsql
> 
> This is part of a function inside a v8.0.2 database.
> 
> I didn't realize that the INTO clause was only limited to one instance.  I was
> trying to accomplish
> 
> SELECT col_a INTO var1,
>        col_b INTO var2,
>        col_c INTO var3,
>        ...
>   FROM foo
>  WHERE fobar;
> 
> Kind Regards,
> Keith

try it like
select col_a,col_b,col_c INTO va1,var2,var3 ....

not sure if 8.0.2 allows you to do that, however.