| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: csv format for psql |
| Date: | 2018-03-09 20:00:43 |
| Message-ID: | CAKFQuwZE=itzNw3R3Z5um3ohGAt8KVq8bUwFEg47w7o2wYJVYg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 9, 2018 at 12:42 PM, Daniel Verite <daniel(at)manitou-mail(dot)org>
wrote:
> I wrote:
>
> > recordsep in the unaligned mode doesn't play the role of a line ending
> > because the last line is not finished by recordsep. According to the
> source
> >code, this is intended, see print_unaligned_text() in print.c:
>
> Something else comes to mind: CSV allows linefeeds inside fields, and
> we don't want to replace these with record separators.
> So the notion that recordsep can be used to choose line endings
> is even less okay than if there was just the last line issue.
>
>
I'm not following - if recordsep is not something that would interpreted as
a newline then the file we output would have not structural newlines. It
might have data newlines but those would be quoted.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-03-09 20:07:50 | Re: FOR EACH ROW triggers on partitioned tables |
| Previous Message | Daniel Verite | 2018-03-09 19:42:36 | Re: csv format for psql |