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

From Scott Mead
Subject Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour
Date
Msg-id d3ab2ec81001131417n20997440ub6becc932bcf242b@mail.gmail.com
Whole thread Raw
In response to R: Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour  (Vincenzo Romano <vincenzo.romano@notorand.it>)
Responses Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour
List pgsql-general

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 SELECTINSERTUPDATE, and DELETE commands. In other statement types (generically called utility statements), you must insert values textually even if they are just data values."

 

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Collate order on Mac OS X, text with diacritics in UTF-8
Next
From: Filip Rembiałkowski
Date:
Subject: Re: log_temp_files confusion