From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Dominique Devienne <ddevienne(at)gmail(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Davin Shearer <scholarsmate(at)gmail(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Emitting JSON to file using COPY TO |
Date: | 2023-11-27 14:43:08 |
Message-ID: | CAKFQuwa=tVQxe0m6tnW-BtLhsGJN0ympLP=WiP+bsbavQU2w4A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Monday, November 27, 2023, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> Hi
>
> po 27. 11. 2023 v 14:27 odesílatel David G. Johnston <
> david(dot)g(dot)johnston(at)gmail(dot)com> napsal:
>
>> On Monday, November 27, 2023, Dominique Devienne <ddevienne(at)gmail(dot)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 “not formatted” 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 wrapper
>> 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.
>
Using LO is, IMO, never the answer. But if you are using a driver API
anyway just handle the normal select query result.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | CG | 2023-11-27 14:51:56 | Re: Removing oids with pg_repack |
Previous Message | Pavel Stehule | 2023-11-27 13:56:30 | Re: Emitting JSON to file using COPY TO |
From | Date | Subject | |
---|---|---|---|
Next Message | Matthias van de Meent | 2023-11-27 14:55:08 | Re: Questions regarding Index AMs and natural ordering |
Previous Message | Nikhil Benesch | 2023-11-27 14:33:45 | Re: pgoutput incorrectly replaces missing values with NULL since PostgreSQL 15 |