| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Zeugswetter Andreas IZ5 <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | "'hackers(at)postgresql(dot)org'" <hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: [HACKERS] psql Week 1 |
| Date: | 1999-10-06 16:34:37 |
| Message-ID: | Pine.LNX.4.10.9910061831100.1744-100000@peter-e.yi.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 6, Zeugswetter Andreas IZ5 mentioned:
> > * when \connect fails, it now keeps the previous connection (formerly
> > aborted program)
>
> This was the behavior at one time, but it was regarded as very dangerous
> and thus changed to the current behavior.
>
> The problem was, that scripts would do things to the wrong database if a
> connect failed.
See earlier response. Only in interactive mode. The idea was that a typo
should not bomb you out of the program.
> The ultimate solution would be an unconnected state, where only
> \connect or help commands would be accepted.
I had that idea, too, but that would open a whole new can of worms
code-wise. Can you guys out there comment if this feature would be
desirable?
--
Peter Eisentraut - peter_e(at)gmx(dot)net
http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-10-06 18:17:20 | Re: [HACKERS] psql and comments |
| Previous Message | Peter Eisentraut | 1999-10-06 16:29:09 | Re: [HACKERS] psql Week 1 |