Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines

Поиск
Список
Период
Сортировка
От Dominique Devienne
Тема Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines
Дата
Msg-id CAFCRh-9Fb97c59NysfYfdVUcKwd3pPfMwTdu5uaEwfPnd7cCCQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines  ("Daniel Verite" <daniel@manitou-mail.org>)
Ответы Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines  (Francisco Olarte <folarte@peoplecall.com>)
Список pgsql-general
On Fri, Mar 11, 2022 at 8:32 PM Daniel Verite <daniel@manitou-mail.org> wrote:
>         Dominique Devienne wrote:
> > so I can easily do that "\n" encoding myself, as a post-processing on
> > the buffer I get back.
>
> Alternatively, it might be easier to use the default TEXT format of
> COPY rather than CSV, as the TEXT format already produces \n for
> line feeds, along with  half a dozen other special backslashes sequences.
> See https://www.postgresql.org/docs/current/sql-copy.html

I actually just submitted CSV+PostProcessing :)

But sure, if TEXT does the kind of pseudo-CSV I need, I'd change it to use it.
I'll look into it next week. Thanks again Daniel. --DD



В списке pgsql-general по дате отправления:

Предыдущее
От: "Daniel Verite"
Дата:
Сообщение: Re: COPY TO STDOUT WITH (FORMAT CSV, HEADER), and embedded newlines
Следующее
От: Michael Lewis
Дата:
Сообщение: Re: foreign key on delete cascade order?