MIME-Version: 1.0
References: <CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU=kcg@mail.gmail.com>
 <b22367ef-6ac1-e1c0-da05-0e760e1b7e29@dunslane.net> <CALvfUkD9ZFUU2pe9RMPqdGaKXu5OZi5xzOiPokGhOoPJ56FgAw@mail.gmail.com>
 <7117a356-916c-4cf3-bad8-861490e65dcf@joeconway.com> <CALvfUkBKTr9WLAbHQYmwZ7SVp5_VDey1F1uCZtKL4+H1-WvyBw@mail.gmail.com>
 <b604b474-e2b2-4ba0-bc60-fd0cbc05cfc9@joeconway.com> <9c77b6fa-ee88-b2e6-0fa7-4fc81721da35@dunslane.net>
 <c30fc5da-0348-4e44-b699-804ccbdcfc36@joeconway.com> <41dcba92-1075-e5e5-cb99-36711abf6cec@dunslane.net>
 <bcbb2a04-5df3-49f2-b304-28ae8edc5189@joeconway.com> <CALvfUkB2QtG-BXsTwjoLO8ZYUsNFytqjPvZex8stQ0r_qNM7HQ@mail.gmail.com>
 <5c84b70b-ba18-c45d-dbbe-612fa229b2ce@dunslane.net> <CALvfUkDxgTppjy-Q_i2znakMFp2vrJdPUEJNyGTL2LcZBOWV6A@mail.gmail.com>
 <cbd65026-d79c-40b1-8be3-10e1db2fc092@joeconway.com> <398c22f6-4299-4b17-80bf-2f14f4afd592@joeconway.com>
 <CALvfUkAbj4Bwg0FjYpvj0-zddcetWg1Sejt=OGBTDskbqOFS_A@mail.gmail.com> <46cc4507-a0d9-4044-b2ce-5a8bca8015c0@joeconway.com>
In-Reply-To: <46cc4507-a0d9-4044-b2ce-5a8bca8015c0@joeconway.com>
From: Davin Shearer <davin@apache.org>
Date: Tue, 5 Dec 2023 14:50:23 -0500
Message-ID: <CALvfUkD8+bcNs1cYeU3wK9YsyZ7zUjs2aTxO+++Vq7zKeUE7+w@mail.gmail.com>
Subject: Re: Emitting JSON to file using COPY TO
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Andrew Dunstan <andrew@dunslane.net>, Joe Conway <mail@joeconway.com>
Content-Type: multipart/alternative; boundary="00000000000048149b060bc88c1e"
Archived-At: <https://www.postgresql.org/message-id/CALvfUkD8%2BbcNs1cYeU3wK9YsyZ7zUjs2aTxO%2B%2B%2BVq7zKeUE7%2Bw%40mail.gmail.com>
Precedence: bulk

--00000000000048149b060bc88c1e
Content-Type: text/plain; charset="UTF-8"

Hi Joe,

In reviewing the 005 patch, I think that when used with FORCE ARRAY, we
should also _imply_ FORCE ROW DELIMITER.  I can't envision a use case where
someone would want to use FORCE ARRAY without also using FORCE ROW
DELIMITER.  I can, however, envision a use case where someone would want
FORCE ROW DELIMITER without FORCE ARRAY, like maybe including into a larger
array.  I definitely appreciate these options and the flexibility that they
afford from a user perspective.

In the test output, will you also show the different variations with FORCE
ARRAY and FORCE ROW DELIMITER => {(false, false), (true, false), (false,
true), (true, true)}?  Technically you've already shown me the (false,
false) case as those are the defaults.

Thanks!

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi Joe,<div><br></div><div>In reviewing t=
he 005 patch, I think that when used with FORCE ARRAY, we should also _impl=
y_ FORCE ROW DELIMITER.=C2=A0 I can&#39;t envision a use case where someone=
 would want to use FORCE ARRAY without also using FORCE ROW DELIMITER.=C2=
=A0 I can, however, envision a use case where someone would want FORCE ROW =
DELIMITER without FORCE ARRAY,=C2=A0like maybe including into a larger arra=
y.=C2=A0 I definitely appreciate these options and the flexibility that the=
y afford from=C2=A0a user perspective.</div><div><br></div><div>In the test=
 output, will you also show the different variations with FORCE ARRAY and F=
ORCE ROW DELIMITER =3D&gt; {(false, false), (true, false), (false, true), (=
true, true)}?=C2=A0 Technically you&#39;ve already shown me the (false, fal=
se) case as those are the defaults.</div><div><br></div><div>Thanks!</div><=
/div></div>

--00000000000048149b060bc88c1e--