| From: | Eugen Konkov <kes-kes(at)yandex(dot)ru> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Proposition for autoname columns |
| Date: | 2020-11-11 18:58:01 |
| Message-ID: | 135468429.20201111205801@yandex.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Bruce,
Wednesday, November 11, 2020, 5:56:08 PM, you wrote:
> On Mon, Nov 2, 2020 at 05:05:29PM +0200, Eugen Konkov wrote:
>> Hello Pgsql-hackers,
>>
>> When selecting data from json column it named as '?column?'
>> tucha=# select info->>'suma', docn from document order by id desc limit 5;
>> ?column? | docn
>> ----------+------
>> 665.97 | 695
>> 513.51 | 632
>> 665.97 | 4804
>> 492.12 | 4315
>> 332.98 | 1302
>> (5 rows)
>>
>> It would be useful if the name of column will be autoassigned based on
>> name of json key. Like at next query:
>>
>> tucha=# select info->>'suma' as suma, docn from document order by id desc limit 5;
>> suma | docn
>> --------+------
>> 665.97 | 695
>> 513.51 | 632
>> 665.97 | 4804
>> 492.12 | 4315
>> 332.98 | 1302
>> (5 rows)
>>
>>
>> Would it be useful this auto assigned name for column from json?
> I think we could do it, but it would only work if the column was output
> as a single json value, and not a multi-key/value field. I am afraid if
> we tried to do it, the result would be too inconsistent to be useful.
cool, thank you.
--
Best regards,
Eugen Konkov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eugen Konkov | 2020-11-11 19:07:09 | Re: Feature request: Improve allowed values for generate series |
| Previous Message | Jacob Champion | 2020-11-11 18:57:02 | Re: Support for NSS as a libpq TLS backend |