Re: proposal - assign result of query to psql variable

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2012-07-26T05:37:40Z
Lists: pgsql-hackers
2012/7/26 Tom Lane <tgl@sss.pgh.pa.us>:
> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> \eset variable [, variable [..]] query --  it raise exception when
>> more than one row is returned or when no row is returned
>
> Better would be a variant on \g, that is you type in the query and
> then tell it where to put the result.  We have learned the hard way
> that putting SQL commands into the arguments of backslash commands
> is a horrid idea.  Maybe
>
>         select x,y,... from ...
>         \gset var1 var2 ...

it could be

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.