| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] psql and libpq fixes |
| Date: | 2000-02-10 20:16:02 |
| Message-ID: | Pine.LNX.4.21.0002102114140.1014-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2000-02-10, Thomas Lockhart mentioned:
> > > > FYI, the commands are
> > > > \set EXIT_ON_ERROR
> > > > and
> > > > \unset EXIT_ON_ERROR
> > > > It's a normal psql variable, but incidentally the syntax seems kind of
> > > > easy to remember.
> > > Can we change that to the more standard ON_ERROR_STOP?
>
> Any chance of multi-word options? Like "\set on error stop"?
You can do
\set 'some string with any character \t\001\n\n' enabled
but that's a little hard to type. ;)
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ross J. Reedstrom | 2000-02-10 21:03:35 | Re: [HACKERS] make_ctags script |
| Previous Message | Peter Eisentraut | 2000-02-10 20:13:42 | psql options |