MIME-Version: 1.0
References: <CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU=kcg@mail.gmail.com>
 <fc1e39f8-274f-4be6-8a70-9fb0d9fe84a2@aklaver.com> <CAFCRh-_LhP5Ln4-beVz=1pQ9VycU3hAxnJHXhPHZRmX0BSCVEQ@mail.gmail.com>
 <CAFCRh--Vhx0105S7SWAYHGcVMTSRtbcoArDUGSbYSWRUGunW_g@mail.gmail.com> <CAKFQuwZb3zaSqkOvGXRRLZEW61az+4xyHZ7tBPR91JfrcdCKvA@mail.gmail.com>
In-Reply-To: <CAKFQuwZb3zaSqkOvGXRRLZEW61az+4xyHZ7tBPR91JfrcdCKvA@mail.gmail.com>
From: Pavel Stehule <pavel.stehule@gmail.com>
Date: Mon, 27 Nov 2023 14:56:30 +0100
Message-ID: <CAFj8pRD-vEAXNew6wu0j9ARhQ_Hu0nwFmGQj0YMQiWw5rQDciQ@mail.gmail.com>
Subject: Re: Emitting JSON to file using COPY TO
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Dominique Devienne <ddevienne@gmail.com>, Adrian Klaver <adrian.klaver@aklaver.com>, 
	Davin Shearer <scholarsmate@gmail.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="00000000000071be64060b22aded"
Archived-At: <https://www.postgresql.org/message-id/CAFj8pRD-vEAXNew6wu0j9ARhQ_Hu0nwFmGQj0YMQiWw5rQDciQ%40mail.gmail.com>
Precedence: bulk

--00000000000071be64060b22aded
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi

po 27. 11. 2023 v 14:27 odes=C3=ADlatel David G. Johnston <
david.g.johnston@gmail.com> napsal:

> On Monday, November 27, 2023, Dominique Devienne <ddevienne@gmail.com>
> wrote:
>
>> There's even a JSON mode.
>> By miracle, would the JSON output mode recognize JSON[B] values, and
>> avoid the escaping?
>>
>
> I agree there should be a copy option for =E2=80=9Cnot formatted=E2=80=9D=
 so if you dump a
> single column result in that format you get the raw unescaped contents of
> the column. As soon as you ask for a format your json is now embedded so =
it
> is a value within another format and any structural aspects of the wrappe=
r
> present in the json text representation need to be escaped.
>

Is it better to use the LO API for this purpose?  It is native for not
formatted data.

Regards

Pavel


> David J.
>

--00000000000071be64060b22aded
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi<br></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">po 27. 11. 2023 v=C2=A014:27 odes=C3=ADlatel =
David G. Johnston &lt;<a href=3D"mailto:david.g.johnston@gmail.com" target=
=3D"_blank">david.g.johnston@gmail.com</a>&gt; napsal:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">On Monday, November 27, 2023, Domini=
que Devienne &lt;<a href=3D"mailto:ddevienne@gmail.com" target=3D"_blank">d=
devienne@gmail.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">There&#39;s even a JSON mode.=
<br></div><div class=3D"gmail_quote"><div>By miracle, would the JSON output=
 mode recognize JSON[B] values, and avoid the escaping?</div></div></div></=
blockquote><div><br></div><div>I agree there should be a copy option for =
=E2=80=9Cnot formatted=E2=80=9D so if you dump a single column result in th=
at format you get the raw unescaped contents of the column. As soon as you =
ask for a format your json is now embedded so it is a value within another =
format and any structural aspects of the wrapper present in the json text r=
epresentation need to be escaped.</div></blockquote><div><br></div><div>Is =
it better to use the LO API for this purpose?=C2=A0 It is native for not fo=
rmatted data. <br></div><div><br></div><div>Regards</div><div><br></div><di=
v>Pavel<br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div><br></div><div>David J.</div>
</blockquote></div></div>

--00000000000071be64060b22aded--