Re: Variable substitution in psql backtick expansion
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Greg Stark <stark@mit.edu>
Cc: Daniel Verite <daniel@manitou-mail.org>, Tom Lane <tgl@sss.pgh.pa.us>,
PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2017-04-11T06:17:57Z
Lists: pgsql-hackers
Hello Greg, >> SELECT some-boolean-expression AS okay \gset >> \if :okay > > Am I the only one who thinks that even if \if got the ability to > evaluate arbitrary SQL queries I would probably still always write > things as above? > I think putting arbitrary SQL expressions (let alone queries) would make > scripts just a total mess and impossible for humans to parse. No. Pavel does not like them. Tom wants them to be eventually possible... However, fine with me if it is decided that there will never be server-side expressions after \if. A good thing is that it potentially simplifies minimal \if client-side expressions. > Whereas storing the results in psql variables and then using those > variables in \if makes even fairly complex queries and nested \if > structures straightforward. It would also make it far clearer in what > order the queries will be evaluated and under which set of conditions. Hmmm. I'm not sure I get it. The penalty I see is that it adds a dummy variable which must be given a sensible name, and for very short expressions this is not a win. But this is a minor point. -- Fabien.
Commits
-
Add psql variables showing server version and psql version.
- a6c678f018d3 10.0 landed
- 9ae9d8c1549c 11.0 landed
-
Reformat psql's --help=variables output.
- 3955c8c4eda2 11.0 landed
-
Remove reinvention of stringify macro.
- cd6baed78150 10.0 landed
-
Allow psql variable substitution to occur in backtick command strings.
- f833c847b8fa 10.0 landed