| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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 20:39:02 |
| Message-ID: | CAFj8pRC0WGwFdxsbxX8wuJ1y6O0Xz5BXq2mh17qLui_QqAeHzQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
2013/2/2 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> writes:
>> On Sat, Feb 2, 2013 at 7:30 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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.
>
> Yeah, I was considering that one too. Let's do it that way.
updated version
Regards
Pavel
>
> regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| gset_20130202.patch | application/octet-stream | 15.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Singer | 2013-02-02 20:43:24 | Re: PL/Python result object str handler |
| Previous Message | Simon Riggs | 2013-02-02 20:11:26 | Re: GetOldestXmin going backwards is dangerous after all |