Re: JSON validation behavior

From: Sergei Kornilov <sk(at)zsrv(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David G(dot) Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: JSON validation behavior
Date: 2018-10-24 16:27:42
Message-ID: 496471540398462@myt6-fe24916a5562.qloud-c.yandex.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

> I could get behind fixing
> it to always throw the error, but that's not what Sergei was hoping for.
On the contrary i think it is reasonable way. It is much better to have error on input value instead of finding wrong value during table processing. We always reject this value for jsonb and i expected the same behavior for json. Not sure about JSON specification compliance, didn't find anything about \u0000 in rfc8259.

regards, Sergei

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-10-24 16:59:04 Re: pgbench - add pseudo-random permutation function
Previous Message Tom Lane 2018-10-24 15:54:33 Re: JSON validation behavior