pg.ddx.io  pgsql-general@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Davin Shearer <davin@apache.org>
To: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: Joe Conway <mail@joeconway.com>
Subject: Re: Emitting JSON to file using COPY TO
Date: Tue, 5 Dec 2023 15:55:53 -0500
Message-ID: <2554e520-e103-8978-dcb5-807dfeb77402@dunslane.net> (raw)
In-Reply-To: <CALvfUkD8+bcNs1cYeU3wK9YsyZ7zUjs2aTxO+++Vq7zKeUE7+w@mail.gmail.com>
References: <CALvfUkBxTYy5uWPFVwpk_7ii2zgT07t3d-yR_cy4sfrrLU=kcg@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>
	<CALvfUkD8+bcNs1cYeU3wK9YsyZ7zUjs2aTxO+++Vq7zKeUE7+w@mail.gmail.com>


On 2023-12-05 Tu 14:50, Davin Shearer wrote:
> 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.
>
>

I don't understand the point of FORCE_ROW_DELIMITER at all. There is 
only one legal delimiter of array items in JSON, and that's a comma. 
There's no alternative and it's not optional. So in the array case you 
MUST have commas and in any other case (e.g. LINES) I can't see why you 
would have them.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com






view thread (163+ messages)  latest in thread

Message-ID: <2554e520-e103-8978-dcb5-807dfeb77402@dunslane.net>
Permalink:  ../2554e520-e103-8978-dcb5-807dfeb77402@dunslane.net/
Also on:    postgresql.org/message-id/2554e520-e103-8978-dcb5-807dfeb77402@dunslane.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-general@postgresql.org
  Cc: andrew@dunslane.net, davin@apache.org, pgsql-hackers@postgresql.org, mail@joeconway.com
  Subject: Re: Emitting JSON to file using COPY TO
  In-Reply-To: <2554e520-e103-8978-dcb5-807dfeb77402@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox