Re: SELECT INTO broken (?) in PL/pgSQL when using a set returning function in FROM clause (BGUG?) - Mailing list pgsql-general

From ezra epstein
Subject Re: SELECT INTO broken (?) in PL/pgSQL when using a set returning function in FROM clause (BGUG?)
Date
Msg-id 6J-dnZUN2uC7R2yiXTWc-g@speakeasy.net
Whole thread Raw
In response to SELECT INTO broken (?) in PL/pgSQL when using a set returning function in FROM clause (BGUG?)  ("ezra epstein" <ee_newsgroup_post@prajnait.com>)
List pgsql-general
Ahhh.  Yes.  A nasty typo.  I did a global search for %1, %2, %3, etc. and
turned up several elsewhere.  Ouch.  Thank you for your close reading.

 == Ezra Epstein

"Tom Lane" <tgl@sss.pgh.pa.us> wrote in message
news:20461.1072368921@sss.pgh.pa.us...
> "ezra epstein" <ee_newsgroup_post@prajnait.com> writes:
> >     IF NOT EXISTS(SELECT 1 FROM merchandise.ds_item($1) WHERE
"client_key" =
> > $2) THEN
> > [ works, but this doesn't: ]
> >     SELECT INTO rec * FROM merchandise.ds_item($1) WHERE "client_key" =
%2;
>
> If that's an accurate transcription, then your error is using %2 where
> you meant $2.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match
>



pgsql-general by date:

Previous
From: treat00@yahoo.com (Thomas Reat)
Date:
Subject: altering a column
Next
From: CoL
Date:
Subject: Re: 'like' refuses to use an index???