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>, David Fetter <david@fetter.org>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2013-02-02T22:12:25Z
Lists: pgsql-hackers 
Pavel Stehule <pavel.stehule@gmail.com> writes:
> 2013/2/2 Tom Lane <tgl@sss.pgh.pa.us>:
>> Shigeru Hanada <shigeru.hanada@gmail.com> writes:
>>> +1 for a).  If users want to determine whether the result was NULL, or
>>> want to use substitute string for NULL result, they can use coalesce
>>> in SELECT clause.  Anyway the feature should be documented clearly.

>> Yeah, I was considering that one too.  Let's do it that way.

> updated version

Applied with corrections.

			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.