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

From Andrew Dunstan
Subject Re: [PATCH] Generalized JSON output functions
Date
Msg-id 55A90D1C.2040000@dunslane.net
Whole thread Raw
In response to Re: [PATCH] Generalized JSON output functions  ("Shulgin, Oleksandr" <oleksandr.shulgin@zalando.de>)
Responses Re: [PATCH] Generalized JSON output functions  (Andrew Dunstan <andrew@dunslane.net>)
Re: [PATCH] Generalized JSON output functions  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 07/17/2015 08:20 AM, Shulgin, Oleksandr wrote:


> > This patch makes Postgres core more complex
>
> Yes, it does. But, that was not the purpose, obviously. :-)
>
> > while not really solving the problem in Javascript.
>
> It still allows for less risk of silent data corruption on the js side.
>
>

I have already pointed out how this patch is fundamentally broken. You 
can achieve your aims by a fairly small amount of code inside your 
logical decoder, and with no core code changes whatsoever. So I'm 
puzzled why we are even still debating this broken design.

cheers

andrew




pgsql-hackers by date:

Previous
From: Fabien
Date:
Subject: pgbench stats per script & other stuff
Next
From: Kevin Grittner
Date:
Subject: Re: [COMMITTERS] pgsql: Retain comments on indexes and constraints at ALTER TABLE ... TY