| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | Bosco Rama <postgres(at)boscorama(dot)com>, pgsql-interfaces(at)postgresql(dot)org, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ecpg 'set' failure using host vars |
| Date: | 2008-08-16 16:01:00 |
| Message-ID: | 14940.1218902460@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
Michael Meskes <meskes(at)postgresql(dot)org> writes:
> Without checking the sources it seems as if PQexecParams is not able to handle a parameter in a set command. Can anyone confirm this?
The backend only supports parameters in plannable statements, ie
SELECT/INSERT/UPDATE/DELETE. (Possibly DECLARE CURSOR, I'm too
lazy to check.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2008-08-16 16:22:16 | Re: Parsing of pg_hba.conf and authentication inconsistencies |
| Previous Message | Tom Lane | 2008-08-16 15:59:23 | Re: proposal sql: labeled function params |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bosco Rama | 2008-08-16 17:16:56 | Re: ecpg 'set' failure using host vars |
| Previous Message | Michael Meskes | 2008-08-16 08:31:56 | Re: ecpg 'set' failure using host vars |