Re: ECPG - connection name in "EXEC SQL AT ... " statement - Mailing list pgsql-interfaces

From Bruce Momjian
Subject Re: ECPG - connection name in "EXEC SQL AT ... " statement
Date
Msg-id 200111021247.fA2Clxv16278@candle.pha.pa.us
Whole thread Raw
In response to Re: ECPG - connection name in "EXEC SQL AT ... " statement  (Edward Pilipczuk <edx@astercity.net>)
List pgsql-interfaces
> On Thursday, 01 November 2001 21:07, you wrote:
> > > Okay, here's the list from the actual TODo file:
> > >
> > > - ecpg should understand structure definitions outside a declare section.
> > > - sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified in a
> > > SET DESCRIPTOR statement will be ignored
> > > - error handling has to be improved by adding additional error-rules to
> > > the parser
> > > - usage of :var[:index] or :var[<integer>] as cvariable for an array var
> > > would be nice
> > > - add a semantic check level, e.g. check if a table really exists
> > > - remove space_or_nl and line_end from pgc.l
> > > - nested C comments do not work
> > > - SQLSTATE is missing
> >
> > OK ecpg/TODO contents move to main TODO list.  Thanks.
> 
> And what about variable in connection name ?

That was already on the TODO list:
       o Allow variable to specify the connection name

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


pgsql-interfaces by date:

Previous
From: Christof Petig
Date:
Subject: Re: ECPG: Automatic Storage allocation for NULL-pointing
Next
From: "Michael Coughlin"
Date:
Subject: error: Relation 'tableName' does not exist ?