Horton
Menu

Re: proposal - assign result of query to psql variable

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Shigeru Hanada <shigeru.hanada@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, Phil Sorber <phil@omniti.com>, Erik Rijkers <er@xs4all.nl>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-02-03T19:02:27Z
Lists: pgsql-hackers 
Pavel Stehule <pavel.stehule@gmail.com> writes:
> now missing variables is replaced by variable's name. We can implement
> some pset option - some like define what do with missing variable

> \pset missing_variable (use_name | use_null | error )

No, it isn't "replaced by variable's name".  What actually happens is we
don't attempt a replacement unless the string after the colon matches an
existing variable.  Tampering with that seems dangerous and foolish.

			regards, tom lane

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix oversight in new code for printing rangetable aliases.