Re: Emitting JSON to file using COPY TO

Поиск
Список
Период
Сортировка
Искать
От
Andrew Dunstan
Тема
Re: Emitting JSON to file using COPY TO
Дата
Msg-id
315b81d4-4b67-7828-0355-3808cd14acd1@dunslane.net
Ответ на
Список
Дерево обсуждения
Re: Emitting JSON to file using COPY TO Joe Conway <mail@joeconway.com>
Re: Emitting JSON to file using COPY TO Joe Conway <mail@joeconway.com>
Re: Emitting JSON to file using COPY TO "David G. Johnston" <david.g.johnston@gmail.com>
Re: Emitting JSON to file using COPY TO Joe Conway <mail@joeconway.com>

On 2023-12-05 Tu 16:09, Joe Conway wrote:
> On 12/5/23 16:02, Joe Conway wrote:
>> On 12/5/23 15:55, Andrew Dunstan wrote:
>>> and in any other case (e.g. LINES) I can't see why you
>>> would have them.
>
> Oh I didn't address this -- I saw examples in the interwebs of MSSQL 
> server I think [1] which had the non-array with commas import and 
> export style. It was not that tough to support and the code as written 
> already does it, so why not?
>
> [1] 
> https://learn.microsoft.com/en-us/sql/relational-databases/json/remove-square-brackets-from-json-without-array-wrapper-option?view=sql-server-ver16#example-multiple-row-result
>
>

That seems quite absurd, TBH. I know we've catered for some absurdity in 
the CSV code (much of it down to me), so maybe we need to be liberal in 
what we accept here too. IMNSHO, we should produce either a single JSON 
document (the ARRAY case) or a series of JSON documents, one per row 
(the LINES case).


cheers


andrew


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



В списке pgsql-hackers по дате отправления
От: Joe Conway
Дата:
От: Masahiko Sawada
Дата:
FAQ