Re: proposal - assign result of query to psql variable

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Phil Sorber <phil(at)omniti(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, David Fetter <david(at)fetter(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal - assign result of query to psql variable
Date: 2013-02-02 22:12:25
Message-ID: 15800.1359843145@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2013/2/2 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2013-02-02 22:33:10 Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system
Previous Message Andres Freund 2013-02-02 21:38:16 Re: logical changeset generation v4 - Heikki's thoughts about the patch state