Re: [HACKERS] ecpg news - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: [HACKERS] ecpg news
Date
Msg-id 199802241605.RAA32606@gauss.topsystem.de
Whole thread Raw
In response to Re: [HACKERS] ecpg news  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
List pgsql-hackers
Thomas G. Lockhart writes:
> The CA-Ingres parameters on "whenever" are only "continue", "stop", "goto
> <label>", and "call <procedure>". I suspect that part of the problem is that
> embedded SQL is available for several host languages, and some don't map the
> same way as C would. How about disabling it for now?

Okay, I will do that as soon as I find time.

> CA-Ingres sez:continue: continues execution with the next executable statement.
> If a fatal error occurs, an error message is printed and the program aborts.
>
> I think this means that errors are ignored, as in Oracle, rather than doing a
> C-style "continue". Then, the program can check the sqlcode variable to decide
> what to do...

Okay, will change that, too. In fact I like this approach much more than the
continue statement.

> The embedded SQL is a great capability which was one of the most visible
> omissions in the Postgres features. Thanks for being so aggressive and
> persistent about getting it solid for its first release. But, we've got to have
> a few things to work on later :)

My pleasure.

Michael

--
Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
meskes@debian.org                      | 52146 Wuerselen
Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10

pgsql-hackers by date:

Previous
From: jwieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh'
Next
From: Hannu Krosing
Date:
Subject: Possible replacement regex