Thanks for all who helped me with this. I just upgraded our one remaining
database to 8.2 and EXECUTE INTO worked great.
THANKS!
Kerri
On 4/22/08, Klint Gore <[EMAIL PROTECTED]> wrote:
>
> Kerri Reno wrote:
>
> > So the reason I'm getting the error is that I'm running it in 8.0.
> > Thanks so m
Kerri Reno wrote:
So the reason I'm getting the error is that I'm running it in 8.0.
Thanks so much for your help!
Kerri
use FOR instead
CREATE OR REPLACE FUNCTION private.get_salary_schedule(integer, text)
RETURNS record AS
$BODY$
declare
tcp_id alias for $1;
tfy alias for $2;
tbl
gt;
> > >
> > >
> > > Jon
> > >
> > >
> > > --
> > >
> > > *From:* [EMAIL PROTECTED] [mailto:
> > > [EMAIL PROTECTED] *On Behalf Of *Kerri Reno
> > > *Sent:* Tuesday, April 22, 20
2008 8:27 AM
To: Roberts, Jon
Cc: pgsql-general@postgresql.org
Subject: Re: FW: Re: [GENERAL] create temp in function
http://www.postgresql.org/docs/8.2/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-EXECUTING-DYN
says
SELECT INTO is not currently supported within EXECUTE.
I was using a te
> >
> > --
> >
> > *From:* [EMAIL PROTECTED] [mailto:
> > [EMAIL PROTECTED] *On Behalf Of *Kerri Reno
> > *Sent:* Tuesday, April 22, 2008 7:55 AM
> > *To:* pgsql-general@postgresql.org
> > *Subject:* Re: FW: Re: [GENERAL]
I tried that, too, and got a different error.
NOTICE: query: select salary_schedule, pay_column, step from saltab07 where
cp_id =32
ERROR: syntax error at or near "$2"
SQL state: 42601
Context: PL/pgSQL function "get_salary_schedule" line 15 at execute
statement
In the PG log file, it sa
D] *On Behalf Of *Kerri Reno
> *Sent:* Tuesday, April 22, 2008 7:55 AM
> *To:* pgsql-general@postgresql.org
> *Subject:* Re: FW: Re: [GENERAL] create temp in function
>
>
>
> Thanks to all who responded. I now know why execute will help this
> problem, but then it causes a new
To: pgsql-general@postgresql.org
Subject: Re: FW: Re: [GENERAL] create temp in function
Thanks to all who responded. I now know why execute will help this problem,
but then it causes a new problem. The example I sent you was trivial, trying
to get to the bottom of the issue. What I'm r
Hello
On 22/04/2008, Kerri Reno <[EMAIL PROTECTED]> wrote:
> Thanks to all who responded. I now know why execute will help this problem,
> but then it causes a new problem. The example I sent you was trivial,
> trying to get to the bottom of the issue. What I'm really trying to is get
> past th
Thanks to all who responded. I now know why execute will help this problem,
but then it causes a new problem. The example I sent you was trivial,
trying to get to the bottom of the issue. What I'm really trying to is get
past the restriction of execute to do SELECT INTO. That's why I created a
-- Original message --
From: "Kerri Reno" <[EMAIL PROTECTED]>
> Adrian,
>
> I don't understand. Why do I need to use execute? It runs fine the first
> time. The second time it bombs, because it's not seeing schedrec
> correctly. Which part should be in an execu
Kerri Reno wrote:
> Adrian,
>
> I don't understand. Why do I need to use execute?
It's a Postgres shortcoming. It's fixed in 8.3 so if it annoys you too
much you can just upgrade.
> It runs fine the first
> time. The second time it bombs, because it's not seeing schedrec
> correctly. Which p
Adrian,
I don't understand. Why do I need to use execute? It runs fine the first
time. The second time it bombs, because it's not seeing schedrec
correctly. Which part should be in an execute query statement?
Thanks!
Kerri
On 4/21/08, Adrian Klaver <[EMAIL PROTECTED]> wrote:
>
> Forgot to hi
Forgot to hit reply all.
- Forwarded Message: --
From: [EMAIL PROTECTED] (Adrian Klaver)
To: "Kerri Reno" <[EMAIL PROTECTED]>
Subject: Re: [GENERAL] create temp in function
Date: Mon, 21 Apr 2008 23:01:53 +
> -- Original message --
> From
14 matches
Mail list logo
