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

From: "ezra epstein" <ee_newsgroup_post(at)prajnait(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: SELECT INTO broken (?) in PL/pgSQL when using a set returning function in FROM clause (BGUG?)
Date: 2003-12-30 20:22:32
Message-ID: 6J-dnZUN2uC7R2yiXTWc-g@speakeasy.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)sss(dot)pgh(dot)pa(dot)us> wrote in message
news:20461(dot)1072368921(at)sss(dot)pgh(dot)pa(dot)us(dot)(dot)(dot)
> "ezra epstein" <ee_newsgroup_post(at)prajnait(dot)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
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Keith C. Perry 2003-12-30 21:21:26 Re: 'like' refuses to use an index???
Previous Message Tom Lane 2003-12-30 20:21:46 Re: 'like' refuses to use an index???