Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From: "Daniel Verite" <daniel@manitou-mail.org>
Subject: Re: Emitting JSON to file using COPY TO
To: "Joe Conway" <mail@joeconway.com>
Cc: Andrew Dunstan <andrew@dunslane.net>,
 Davin Shearer <davin@apache.org>,
 PostgreSQL-development <pgsql-hackers@postgresql.org>
In-Reply-To: <4162f7f7-6fd6-4720-98e2-89f80e3de2ed@joeconway.com>
Date: Fri, 08 Dec 2023 20:45:23 +0100
Message-Id: <bfb8b746-148a-47e4-a5c1-51156bcb7e89@manitou-mail.org>
Archived-At: 
 <https://www.postgresql.org/message-id/bfb8b746-148a-47e4-a5c1-51156bcb7e89%40manitou-mail.org>
Precedence: bulk

	Joe Conway wrote:

> copyto_json.007.diff

When the source has json fields with non-significant line feeds, the COPY
output has these line feeds too, which makes the output incompatible
with rule #2 at https://jsonlines.org  ("2. Each Line is a Valid JSON
Value").

create table j(f json);

insert into j values('{"a":1,
"b":2
}');

copy j to stdout (format json);

Result:
{"f":{"a":1,
"b":2
}}

Is that expected? copy.sgml in 007 doesn't describe the output
in terms of lines so it's hard to tell from the doc.


Best regards,
--=20
Daniel V=E9rit=E9
https://postgresql.verite.pro/
Twitter: @DanielVerite