| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL <pgsql-hackers(at)postgresql(dot)org>, <pgsql-hackers-owner(at)postgresql(dot)org> |
| Subject: | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Date: | 2017-02-01 21:58:36 |
| Message-ID: | b52a4e15-8a6a-a3d5-0e92-76263a998829@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/1/17 12:03 PM, Fabien COELHO wrote:
> I'm unsure whether it is a good idea, I like terse interfaces, but this
> is just an opinion.
I think the issue here is that the original case for this is a user
accidentally getting into an \if and then having no clue what's going
on. That's similar to what happens when you miss a quote or a semicolon.
We handle those cases with %R, and I think %R needs to support if as well.
Perhaps there's value to providing more info (active branch, etc), but
ISTM trying to do that will just confuse the original (%R) case.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-02-01 22:01:22 | Re: Refactoring of replication commands using printsimple |
| Previous Message | David Fetter | 2017-02-01 21:56:31 | Re: [COMMITTERS] pgsql: Make psql's \set display variables in alphabetical order. |