Message-ID: <d95ea203-ed42-4397-ec4e-6cc26a8598f4@dunslane.net>
Date: Thu, 28 Apr 2022 15:35:24 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: json_object returning jsonb reuslt different from returning json,
 returning text
Content-Language: en-US
From: Andrew Dunstan <andrew@dunslane.net>
To: alias <postgres.rocks@gmail.com>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
References: <CAJA4AWQ_XbSmsNbW226UqNyRLJ+wb=iQkQMj77cQyoNkqtf=2Q@mail.gmail.com>
 <CAJA4AWTJWt06LA5CAxuFb39X5KmD8fF0JeC1Qrb_jXuR8Lvcyg@mail.gmail.com>
 <2a30c387-3c59-59a2-cd24-e85b7ab17e80@dunslane.net>
In-Reply-To: <2a30c387-3c59-59a2-cd24-e85b7ab17e80@dunslane.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/d95ea203-ed42-4397-ec4e-6cc26a8598f4%40dunslane.net>
Precedence: bulk


On 2022-04-25 Mo 10:14, Andrew Dunstan wrote:
> On 2022-04-25 Mo 01:19, alias wrote:
>> seems it's a bug around value 0.
>>
>> SELECT JSON_OBJECTAGG(k: v ABSENT ON NULL WITH UNIQUE KEYS RETURNING
>> jsonb)
>> FROM (VALUES (1, 1), (10, NULL),(4, null), (5, null),(6, null),(2, 2))
>> foo(k, v);
>> return:
>> {"1": 1, "2": 2}
>>
>> SELECT JSON_OBJECTAGG(k: v ABSENT ON NULL WITH UNIQUE KEYS RETURNING
>> jsonb)
>> FROM (VALUES (1, 1), (0, NULL),(4, null), (5, null),(6, null),(2, 2))
>> foo(k, v);
>>
>> return
>>  {"0": null, "1": 1, "2": 2}
>
> Thanks for the report.
>
> I don't think there's anything special about '0' except that it sorts
> first. There appears to be a bug in the uniquefying code where the first
> item(s) have nulls. The attached appears to fix it. Please test and see
> if you can break it.


Fix pushed.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com