| From: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
|---|---|
| To: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: R: Re: R: Re: Weird EXECUTE ... USING behaviour |
| Date: | 2010-01-13 22:17:51 |
| Message-ID: | d3ab2ec81001131417n20997440ub6becc932bcf242b@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jan 13, 2010 at 11:00 PM, Vincenzo Romano <
vincenzo(dot)romano(at)notorand(dot)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."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Filip Rembiałkowski | 2010-01-13 22:37:06 | Re: log_temp_files confusion |
| Previous Message | Martijn van Oosterhout | 2010-01-13 22:02:18 | Re: Collate order on Mac OS X, text with diacritics in UTF-8 |