Re: [PATCH] Generalized JSON output functions - Mailing list pgsql-hackers

From Shulgin, Oleksandr
Subject Re: [PATCH] Generalized JSON output functions
Date
Msg-id CACACo5S0C47a0JwRUYDVY2ALM-BoVu2GkOUJNndzaKR8yTdh_Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Generalized JSON output functions  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
<p dir="ltr">> Yes, but I think the plugin is the right place to do it. What is more, this won't actually prevent
youcompletely from producing non-ECMAScript compliant JSON, since json or jsonb values containing offending numerics
won'tbe caught, AIUI.<p dir="ltr">Ah, that's a good catch indeed.<p dir="ltr">> But a fairly simple to write
functionthat reparsed and fixed the JSON inside the decoder would work.<p dir="ltr">Need to rethink this, but reparsing
wasnever my favorite option here. :-)<p dir="ltr">--<br /> Alex<br /> 

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: TABLESAMPLE doesn't actually satisfy the SQL spec, does it?
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] BUG #13126: table constraint loses its comment