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: Tom Lane <tgl@sss.pgh.pa.us>, 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-02T14:43:46Z
Lists: pgsql-hackers 
2013/2/2 Shigeru Hanada <shigeru.hanada@gmail.com>:
> On Sat, Feb 2, 2013 at 7:30 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> possible variants
>>
>> a) don't store NULL  values - and remove existing variable when NULL
>> be assigned - it is probably best, but should be confusing for users
>> b) implement flag IS NULL - for variables
>> c) use nullPrint
>> d) use empty String
>
> +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.
>

yes, this has one other advantage - it doesn't block possible
enhancing variables about NULL support in future. And other - it
doesn't depends on psql settings

Regards

Pavel

> --
> Shigeru HANADA

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.