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 200111012007.fA1K7ZV25508@candle.pha.pa.us
Whole thread Raw
In response to Re: ECPG - connection name in "EXEC SQL AT ... " statement  (Michael Meskes <meskes@postgresql.org>)
Responses Re: ECPG - connection name in "EXEC SQL AT ... " statement  (Edward Pilipczuk <edx@astercity.net>)
List pgsql-interfaces
> On Wed, Oct 31, 2001 at 08:52:17AM +0100, Christof Petig wrote:
> > > 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.
> 
> I agree.
> 
> > I'd second that move. But Michaels (maintainer) vote on this is stronger than mine
> > (contributor).
> 
> :-)
> 
> 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.

--  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: Antonio Sergio de Mello e Souza
Date:
Subject: Re: getting started with libpq and postgresql
Next
From: Ludek Finstrle
Date:
Subject: Re: Need Help with BLOBs via DBI