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

Added to TODO. Also, do we still use interfaces/ecpg/TODO. Seems we
should roll that into the main TODO like we did with jdbc.

---------------------------------------------------------------------------

> Bruce Momjian wrote:
>
> > > 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?
>
> I can give you several TODO lines for ecpg (including this one)
>
> - implement set descriptor, using descriptor
> - make casts work in variable initializations
> - allow variable to specify the connection name << this is it
> - implement SQLDA (isn't that already in the TODO list?)
> - design a way to select an array of strings into a variable without the need to
> specify maximum length and count of strings
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

--
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