| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql variables |
| Date: | 2004-02-09 20:01:21 |
| Message-ID: | 22961.1076356881@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Shell variables did serve as a design model, mostly because I found it
> better to use *some* model rather than inventing behavior out of thin
> air. Consequently, I am sort of biased on this.
It does seem worth pointing out that shell variables have acted the way
they do for a long time. I haven't heard all that many people
complaining about it, so I'm unconvinced that the behavior is broken.
I'm definitely against breaking backwards compatibility to improve it
in psql.
I might be willing to support an optional (not-default) mode with more
error checking, though. What did you think of the "\declare foo" idea?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2004-02-09 20:09:34 | Re: Two-phase commit |
| Previous Message | Tom Lane | 2004-02-09 19:51:30 | Re: 7.4.1 release status - Turkish Locale |