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

Re: ECPG - connection name in "EXEC SQL AT ... " statement

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: ECPG - connection name in "EXEC SQL AT ... " statement
Date: 2001-10-23 16:45:50
Message-ID: 200110231645.f9NGjpL04950@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
> On Mon, Oct 22, 2001 at 10:34:59AM +0200, Edward Pilipczuk wrote:
> > I've faced with the problem when trying to pass dynamically connection name 
> > to DB into the "EXEC SQL AT ..." statement.
> 
> Hmm, the AT statement was never designed to get a dynamic connection name.
> It appears there was some interaction with other changes.
> 
> > { ECPGdo(__LINE__, dbcn, "select value from table_name where key  = ?  ", 
> 
> It did accept "dbcn" as connection name, but also add it to the variable
> list, which of course is not correct.
> 
> > Is there any other solution ?
> 
> Use a static connection name? :-)
> 
> Just joking, this is a bug that has to be fixed.

Can I have a TODO line for this fix?

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

Responses

pgsql-interfaces by date

Next:From: Christof PetigDate: 2001-10-24 11:27:48
Subject: ECPG: Automatic Storage allocation for NULL-pointing output variables
Previous:From: Tushar NerurkarDate: 2001-10-23 16:24:57
Subject: pgadmin for postgresql 7.0

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