Skip site navigation (1) Skip section navigation (2)

Re: ecpg 'set' failure using host vars

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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
>> 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 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!

In response to

pgsql-hackers by date

Next:From: Steve AtkinsDate: 2008-08-18 15:12:53
Subject: Re: Overhauling GUCS
Previous:From: Bruce MomjianDate: 2008-08-18 14:53:51
Subject: Re: [COMMITTERS] pgsql: Make the pg_stat_activity view call a SRF

pgsql-interfaces by date

Next:From: Michael MeskesDate: 2008-08-19 10:31:18
Subject: Re: ecpg 'set' failure using host vars
Previous:From: Bosco RamaDate: 2008-08-16 17:20:42
Subject: Re: ecpg 'set' failure using host vars

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group