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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Michael Meskes <meskes(at)postgresql(dot)org>
Cc: Christof Petig <christof(at)petig-baender(dot)de>, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: ECPG - connection name in "EXEC SQL AT ... " statement
Date: 2001-11-01 20:07:35
Message-ID: 200111012007.fA1K7ZV25508@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(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

In response to

Responses

Browse pgsql-interfaces by date

  From Date Subject
Next Message Antonio Sergio de Mello e Souza 2001-11-01 20:45:33 Re: getting started with libpq and postgresql
Previous Message Jeremy Wohl 2001-11-01 12:59:05 Re: Inserting/updating large text fields w/libpq -- Please ignore