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

> 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@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026