| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Sehrope Sarkuni <sehrope(at)jackdb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Davin Shearer <davin(at)apache(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Emitting JSON to file using COPY TO |
| Date: | 2023-12-06 22:56:22 |
| Message-ID: | CAKFQuwaw+n=FBLUXs-jPQbcrvN9Bmgu6eTM-q+GpnHpKBDUsJg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, Dec 6, 2023 at 3:38 PM Joe Conway <mail(at)joeconway(dot)com> wrote:
> So the questions are:
> 1. Do those two formats work for the initial implementation?
>
Yes. We provide a stream-oriented format and one atomic-import format.
2. Is the default correct or should it be switched
> e.g. rather than specifying FORCE_ARRAY to get an
> array, something like FORCE_NO_ARRAY to get JSON lines
> and the JSON array is default?
>
>
No default?
Require explicit of a sub-format when the main format is JSON.
JSON_OBJECT_ROWS
JSON_ARRAY_OF_OBJECTS
For a future compact array-structured-composites sub-format:
JSON_ARRAY_OF_ARRAYS
JSON_ARRAY_ROWS
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2023-12-06 23:09:30 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Joe Conway | 2023-12-06 22:38:21 | Re: Emitting JSON to file using COPY TO |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2023-12-06 23:09:30 | Re: Emitting JSON to file using COPY TO |
| Previous Message | Joe Conway | 2023-12-06 22:38:21 | Re: Emitting JSON to file using COPY TO |