Horton
Menu

Re: proposal - assign result of query to psql variable

Pavel Stehule <pavel.stehule@gmail.com>

View thread
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Shigeru Hanada <shigeru.hanada@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>, Phil Sorber <phil@omniti.com>, Erik Rijkers <er@xs4all.nl>, David Fetter <david@fetter.org>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-02-01T05:22:59Z
Lists: pgsql-hackers 
Hello

can you look, please, on updated version - it respects Tom's proposal
and it is significantly reduced?

Thank you

Pavel Stehule

2013/1/28 Pavel Stehule <pavel.stehule@gmail.com>:
> Hello
>
> 2013/1/26 Tom Lane <tgl@sss.pgh.pa.us>:
>> Andrew Dunstan <andrew@dunslane.net> writes:
>>> +1. This looks quite nifty. Maybe useful too to have a default prefix
>>> via some setting.
>>
>> Meh.  I would expect that "\gset :foo" would work to specify a computed
>> prefix if you wanted it --- isn't that sufficient indirection?  I'm not
>> thrilled with further expanding the set of magic variables in psql.
>>
>
> here is patch related to your proposal
>
> Regards
>
> Pavel
>
>>                         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.