| From: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Ryan Pedela <rpedela(at)datalanche(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, hlinnaka(at)iki(dot)fi, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Generalized JSON output functions |
| Date: | 2015-07-14 06:32:51 |
| Message-ID: | CACACo5S0C47a0JwRUYDVY2ALM-BoVu2GkOUJNndzaKR8yTdh_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Yes, but I think the plugin is the right place to do it. What is more,
this won't actually prevent you completely from producing non-ECMAScript
compliant JSON, since json or jsonb values containing offending numerics
won't be caught, AIUI.
Ah, that's a good catch indeed.
> But a fairly simple to write function that reparsed and fixed the JSON
inside the decoder would work.
Need to rethink this, but reparsing was never my favorite option here. :-)
--
Alex
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-07-14 07:29:13 | Re: BUG #13126: table constraint loses its comment |
| Previous Message | Simon Riggs | 2015-07-14 06:31:35 | Re: TABLESAMPLE doesn't actually satisfy the SQL spec, does it? |