From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | psql - add ability to test whether a variable exists |
Date: | 2017-08-26 06:54:24 |
Message-ID: | alpine.DEB.2.20.1708260835520.3627@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello,
As a follow-up to the \if patch by Corey Huinker, here is a proposal to
allow testing whether a client-side variable exists in psql.
The syntax is as ugly as the current :'var' and :"var" things, but ISTM
that this is the only simple option to have a working SQL-compatible
syntax with both client-side substitution and server side execution. See
the second example below.
-- client side use
psql> \set i 1
psql> \if :?i?
psql> \echo 'i is defined'
psql> \endif
-- use server-side in an SQL expression
psql> SELECT NOT :?VERSION_NUM? OR :'VERSION' <> VERSTION() AS bad_conf \gset
psql> \if :bad_conf \echo 'too bad...' \quit \endif
The other option would be to have some special keyword syntax, say
"defined var", but then it would have to be parsed client side, and how to
do that in an SQL expression is unclear, and moreover it would not look
right in an SQL expression. If it would look like a function call, say
"defined('var')", it would potentially interact with existing server-side
user-defined functions, which is pretty undesirable. Hence the :?...?
proposal above which is limited to variable subsitution syntax.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
psql-ifdef-1.sql | application/x-sql | 5.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2017-08-26 07:44:30 | Re: psql - add ability to test whether a variable exists |
Previous Message | Fabien COELHO | 2017-08-26 06:08:50 | Re: Variable substitution in psql backtick expansion |