| 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: | Serguei Mokhov <sa_mokho(at)alcor(dot)concordia(dot)ca>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Subject: | Re: psql misbehaves because of a simple typo |
| Date: | 2001-12-28 04:20:33 |
| Message-ID: | 200112280420.fBS4KX125359@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > The fact that backslash commands inside parens clear the
> > counter is a minor anoyance but resonable behavior.
>
> If they cleared the command buffer too, it might be construed
> as novice-friendly behavior (though I'd still call it broken).
> However, letting the counter get out of sync with the buffer
> contents cannot be called anything but a bug.
OK, so what do we want to do? Clearing the buffer on a any backslash
command is clearly not what we want to do. Should we clear the buffer
on a backslash command _only_ if the number of paren's is not even? If
we don't clear the counter on a backslash command with uneven parens, do
we risk trapping people in psql?
--
Bruce Momjian | http://candle.pha.pa.us
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-12-28 04:22:38 | Re: psql misbehaves because of a simple typo |
| Previous Message | Hiroshi Inoue | 2001-12-28 04:13:31 | Re: Glitches in heapam.c xlog redo routines |