[pgAdmin4][RM3587] Browser rendering of a bigint in a jsonb is wrong

From: Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>
To: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: [pgAdmin4][RM3587] Browser rendering of a bigint in a jsonb is wrong
Date: 2019-02-26 08:55:02
Message-ID: CAM9w-_mLA=x_f_2budz2iEqc2Mp8dcM9XjqD6R5RsCkU5ndZsg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi Hackers,

Attached is the patch to fix incorrect rendering of bigint in jsonb.
The problem is in javascript limitations with big numbers. For fixing,
jsonb data will be fetched as string now, similar to json, so that JS will
not consider big numbers as number. The only drawback here is that, the
popup editor will not show formatted json, as that requires JSON.parse
which will change the big numbers.

Kindly review.

Below is sample data for testing:
CREATE TABLE public.tab_jsonbigint
(
id integer NOT NULL PRIMARY KEY,
coljsonb jsonb
)

insert into tab_jsonbigint(id, coljsonb) values(3,'[{"a":
83136002445762248}, {"a": 831360024457622448}]');

select d.*, t.coljsonb from tab_jsonbigint t,
jsonb_to_recordset(t.coljsonb) as d("a" bigint);

--
Thanks and Regards,
Aditya Toshniwal
Software Engineer | EnterpriseDB Software Solutions | Pune
"Don't Complain about Heat, Plant a tree"

Attachment Content-Type Size
RM3587.patch application/octet-stream 2.3 KB

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Khushboo Vashi 2019-02-26 09:01:10 [pgAdmin4][Patch] - Encoding Fixes
Previous Message Dave Page 2019-02-25 17:08:09 pgAdmin 4 commit: Fix the text highlight colour.