From: | Michael Meskes <meskes(at)topsystem(dot)de> |
---|---|
To: | lockhart(at)alumni(dot)caltech(dot)edu (Thomas G(dot) Lockhart) |
Cc: | pgsql-hackers(at)postgresql(dot)org (PostgreSQL Hacker) |
Subject: | Re: [HACKERS] ecpg news |
Date: | 1998-02-24 16:05:34 |
Message-ID: | 199802241605.RAA32606@gauss.topsystem.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)topsystem(dot)de | Europark A2, Adenauerstr. 20
meskes(at)debian(dot)org | 52146 Wuerselen
Go SF49ers! Go Rhein Fire! | Tel: (+49) 2405/4670-44
Use Debian GNU/Linux! | Fax: (+49) 2405/4670-10
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 1998-02-24 16:08:06 | Possible replacement regex |
Previous Message | Jan Wieck | 1998-02-24 15:58:07 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/bin/initdb initdb.sh' |