From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Undefined psql variables |
Date: | 2017-01-23 17:53:11 |
Message-ID: | 11154.1485193991@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
> I was giving some thought to how psql handles undefined variables.
> I would like an option where either psql can provide an alternate value
> when an undefined variable is referenced, or a way to detect that a
> specific variable is undefined and replace it with a defined variable.
This seems pretty bizarre. What's the use case? Why would it not
be better to build the behavior out of other spare parts, along the
lines of COALESCE or perhaps
\if not defined(x)
\set x y
\fi
Obviously the \if stuff is things we don't have yet either, but
it seems less likely to have surprising side-effects.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2017-01-23 18:03:03 | Re: Online enabling of page level checksums |
Previous Message | Corey Huinker | 2017-01-23 17:52:27 | Re: Undefined psql variables |