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

From Michael Meskes
Subject Re: ECPG - connection name in "EXEC SQL AT ... " statement
Date
Msg-id 20011101111552.F2224@feivel.fam-meskes.de
Whole thread Raw
In response to Re: ECPG - connection name in "EXEC SQL AT ... " statement  (Christof Petig <christof@petig-baender.de>)
Responses Re: ECPG - connection name in "EXEC SQL AT ... " statement  (Bruce Momjian <pgman@candle.pha.pa.us>)
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

Michael
-- 
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!


pgsql-interfaces by date:

Previous
From: Michael Meskes
Date:
Subject: Re: ECPG: Automatic Storage allocation for NULL-pointing
Next
From: Jeremy Wohl
Date:
Subject: Re: Inserting/updating large text fields w/libpq -- Please ignore