Re: Variable substitution in psql backtick expansion - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Variable substitution in psql backtick expansion
Date
Msg-id alpine.DEB.2.20.1704032126450.23892@lancre
Whole thread Raw
In response to Re: Variable substitution in psql backtick expansion  ("Daniel Verite" <daniel@manitou-mail.org>)
List pgsql-hackers

> [...] but OTOH "\if sql 1 from table where expr" looks awkward. Given an 
> implicit select, I would prefer "\if exists (select 1 from table where 
> expr)" but now it's not shorter.

Possibly, but it is just an SQL expression, which looks good in the middle 
of an sql script.

> An advantage of prepending the SELECT automatically, is that it
> would prevent people from abusing this syntax by putting
> update/insert/delete or even DDL in there, imagining that this would
> be a success/failure test for these operations.

> Having these fail to execute in the first place, when called by \if,
> seems like a sane failure mode that we would gain incidentally.

Yes, it should be avoided.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [PATCH] few fts functions for jsonb
Next
From: Andres Freund
Date:
Subject: Re: parallel explain analyze support not exercised