| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL EXECUTE '..' USING with unknown |
| Date: | 2010-08-05 21:31:49 |
| Message-ID: | 4C5B2DC5.2030804@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/05/2010 05:11 PM, Tom Lane wrote:
> Heikki Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> There's a little problem with EXECUTE USING when the parameters are of
>> type unknown (going back to 8.4 where EXECUTE USING was introduced):
>> do $$
>> BEGIN
>> EXECUTE 'SELECT to_date($1, $2)' USING '17-DEC-80', 'DD-MON-YY';
>> END;
>> $$;
>> ERROR: failed to find conversion function from unknown to text
> This example doesn't seem terribly compelling. Why would you bother
> using USING with constants?
>
>
In a more complex example you might use $1 in more than one place in the
query.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian Pflug | 2010-08-05 22:05:24 | Re: Patch to show individual statement latencies in pgbench output |
| Previous Message | Tom Lane | 2010-08-05 21:11:41 | Re: PL/pgSQL EXECUTE '..' USING with unknown |