From: Keith Worthington <keithw@narrowpathinc.com>
To: PostgreSQL SQL <pgsql-sql@postgresql.org>
Subject: Re: "CASE" is not a variable
Date: Wed, 28 Jun 2006 13:34:58 -0400
Message-ID: <20060628173010.M51266@narrowpathinc.com> (raw)
In-Reply-To: <21800.1151511389@sss.pgh.pa.us>
References: <20060628154728.M33440@narrowpathinc.com>
<21800.1151511389@sss.pgh.pa.us>
> > "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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: keithw@narrowpathinc.com
Subject: Re: "CASE" is not a variable
In-Reply-To: <20060628173010.M51266@narrowpathinc.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox