From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | Bosco Rama <postgres(at)boscorama(dot)com> |
Cc: | pgsql-interfaces(at)postgresql(dot)org |
Subject: | Re: ecpg 'set' failure using host vars |
Date: | 2008-08-18 14:58:21 |
Message-ID: | 20080818145821.GA5062@feivel.credativ.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
>>> 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.)
>
> Thanks for the hint guys. I used a prepare/execute pair instead and
> it worked a treat. More cumbersome but it gets the job done.
I will fix this as soon as my time permits. There is logic there in ecpg to
handle parameters on the client side.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2008-08-18 15:12:53 | Re: Overhauling GUCS |
Previous Message | Bruce Momjian | 2008-08-18 14:53:51 | Re: [COMMITTERS] pgsql: Make the pg_stat_activity view call a SRF |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2008-08-19 10:31:18 | Re: ecpg 'set' failure using host vars |
Previous Message | Bosco Rama | 2008-08-16 17:20:42 | Re: ecpg 'set' failure using host vars |