From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: jsonb_strip_nulls with arrays? |
Date: | 2025-02-19 22:18:58 |
Message-ID: | 2a3a38fb-818f-491f-bcd5-0c0672c874f2@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2025-02-19 We 4:23 PM, Florents Tselai wrote:
>
>
>> On 18 Jan 2025, at 11:51 AM, Florents Tselai
>> <florents(dot)tselai(at)gmail(dot)com> wrote:
>>
>>
>>
>>> On 8 Jan 2025, at 6:45 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>>>
>>>
>>> On 2024-09-17 Tu 4:53 PM, Florents Tselai wrote:
>>>>
>>>> We could, if we're going to do anything at all in this area.
>>>> Another possibility would be to provide a second optional
>>>> parameter for json{b}_strip_nulls. That's probably a better way
>>>> to go.
>>>>
>>>> Here's a patch that adds that argument (only for jsonb; no json
>>>> implementation yet)
>>>>
>>>>
>>>
>>> I think it looks sane. We're not stripping a top level null, which
>>> is one thing I looked out for.
>>>
>>> I think we need a json implementation as well, though.
>>>
>>>
>> Thanks for having a Look, Andrew;
>> if there aren’t any other objections, I’ll come back with a json
>> implementation too.
>
> Attached is a v2 patch with the missing json implementation.
> jsonb one remains the same.
Please add this to the next Commitfest at
https://commitfest.postgresql.org/52/
cheers
andrew
>
>
>
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2025-02-19 22:33:27 | Re: new commitfest transition guidance |
Previous Message | Jelte Fennema-Nio | 2025-02-19 22:18:36 | Re: new commitfest transition guidance |