Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour - Mailing list pgsql-general

From Adrian Klaver
Subject Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour
Date
Msg-id 201001131710.37789.adrian.klaver@gmail.com
Whole thread Raw
In response to Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour  (Scott Mead <scott.lists@enterprisedb.com>)
Responses Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour  (Vincenzo Romano <vincenzo.romano@notorand.it>)
List pgsql-general
On Wednesday 13 January 2010 2:17:51 pm Scott Mead wrote:
> On Wed, Jan 13, 2010 at 11:00 PM, Vincenzo Romano <
>
> vincenzo.romano@notorand.it> wrote:
> > It is not the check or the select.
> > It is the way the substitution has been implemented. It looks like the
> > code replaces the variable name and not the value.
> > Which is different from what is written at page 800.
> > I only hope they won't change the manual to match the feature/bug
> > (warning: new joke)
>
> Page 800:
>
> "Another restriction on parameter symbols is that they only work in SELECT,
> INSERT, UPDATE, and DELETE commands. In other statement types (generically
> called utility statements), you must insert values textually even if they
> are just data values."

Scott, thanks for that I must have read through that section several times at
least with out picking up on it.

--
Adrian Klaver
adrian.klaver@gmail.com

pgsql-general by date:

Previous
From: Yan Cheng Cheok
Date:
Subject: Re: Extremely Slow Cascade Delete Operation
Next
From: "Joshua D. Drake"
Date:
Subject: PgEast CFP (second call)