Horton
Menu

Re: proposal - assign result of query to psql variable

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pavel Stehule <pavel.stehule@gmail.com>, Shigeru Hanada <shigeru.hanada@gmail.com>, Phil Sorber <phil@omniti.com>, Erik Rijkers <er@xs4all.nl>, David Fetter <david@fetter.org>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-01-26T17:04:35Z
Lists: pgsql-hackers 
On 01/26/2013 11:42 AM, Tom Lane wrote:

> A probably-useful extension to this basic concept is to allow \gset
> to specify an optional prefix, that is
> 	select 1 as x, 2 as y \gset p_
> would set p_x and p_y.  This would make it easier to manage results from
> multiple \gset operations, and to be sure that you didn't accidentally
> overwrite some built-in variable.

+1. This looks quite nifty. Maybe useful too to have a default prefix 
via some setting.


cheers

andrew

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.