Re: proposal - assign result of query to psql variable - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: proposal - assign result of query to psql variable
Date
Msg-id CAFj8pRA_f_wg0dhTaVO8rGdbeJN+XarW9rSCDjk1KGrUDSgg+Q@mail.gmail.com
Whole thread Raw
In response to Re: proposal - assign result of query to psql variable  (Pavel Stehule <pavel.stehule@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Next
From: Pavel Stehule
Date:
Subject: Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used