| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: Variable substitution in psql backtick expansion |
| Date: | 2017-04-02 06:53:25 |
| Message-ID: | alpine.DEB.2.20.1704020841490.4632@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bonjour Daniel,
> I think that users would rather have the option to just put
> an SQL expression behind \if.
Note that this is already available indirectly, as show in the
documentation.
SELECT some-boolean-expression AS okay \gset
\if :okay
\echo boolean expression was true
\else
\echo boolean expression was false
\endif
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-04-02 06:58:28 | Re: Variable substitution in psql backtick expansion |
| Previous Message | Andres Freund | 2017-04-02 00:54:45 | Re: New expression evaluator and indirect jumps |