Re: [HACKERS] psql and libpq fixes

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] psql and libpq fixes
Date: 2000-02-08 16:38:53
Message-ID: 200002081638.LAA29046@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> But on third thought, probably the thing that would be really useful
> for "expected errors" is if there is a backslash-command that turns on
> or off the kill-on-error behavior. (The command line switch would
> merely set the initial state of this flag.) This way, a script could
> use the option in an intelligent fashion:
>
> \kill-on-error off
> DROP TABLE t1;
> \kill-on-error on
> CREATE TABLE t1;
> ...
>
> It'd still have to default to 'off' for backwards compatibility,
> unfortunately, but something like this would be really useful.

In Informix 4GL, it is ON ERROR STOP and ON ERROR CONTINUE.

--
Bruce Momjian | http://www.op.net/~candle
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-02-08 16:41:58 Re: [HACKERS] Deferred trigger queue
Previous Message Bruce Momjian 2000-02-08 16:38:02 Re: [HACKERS] Ordering of pg_dump output