From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: row_to_array function |
Date: | 2015-01-17 06:26:33 |
Message-ID: | CAFj8pRBxpQb4GAgwaERwZ=BuA1mFi3LHc8ghFC17hzDBCUfK_w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-01-16 22:35 GMT+01:00 Andrew Dunstan <andrew(at)dunslane(dot)net>:
>
> On 01/16/2015 12:22 PM, Pavel Stehule wrote:
>
>>
>>
>> There two possible transformations:
>>
>> row_to_array --> [[key1, value1],[key2, value2], ...]
>> row_to_row_array --> [(key1, value1), (key2, value2), ... ]
>>
>>
>> If we're going to go that route, I think it makes more sense to
>> create an actual key/value type (ie:
>> http://pgxn.org/dist/pair/doc/pair.html) and return an array of that.
>>
>>
>> ok
>>
>> <http://BlueTreble.com>
>>
>>
>
> I think we'd possibly be better off with simply returning a flat array,
> [key1, value1, ...]
>
> Thats's what the hstore(text[]) and json_object(text[]) functions accept,
> along with the 2D variant, if we want a precedent.
>
It can be one of supported variant. I should not be one, because we cannot
to simply iterate over it
Next possibility is teach FOREACH to take key and value in one step.
Regards
Pavel
>
> cheers
>
> andrew
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-01-17 06:32:05 | Re: proposal: lock_time for pg_stat_database |
Previous Message | David Johnston | 2015-01-17 05:24:33 | Re: Merging postgresql.conf and postgresql.auto.conf |