From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Andrea Riciputi <andrea(dot)riciputi(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Extending COPY TO |
Date: | 2014-09-23 06:56:19 |
Message-ID: | 20140923065619.GU16422@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrea,
* Andrea Riciputi (andrea(dot)riciputi(at)gmail(dot)com) wrote:
> My idea was to extend the COPY TO command to accept an EOL option as it already does with the DELIMITER option. To keep it simple we can limit the EOL choice to CR, LF or CRLF to avoid unusual output, and also keep the current behaviour when no EOL option is given. I was also wondering if an EOL option could be useful also for the text output format or not.
Have you considered using COPY TO's 'PROGRAM' option to simply pipe the
output through unix2dos..?
> I spent the weekend reading the COPY command source code and its grammar definition and I think I can patch it by myself, submit the patch here and wait for your review. However before starting this in my spare time I wanted to know if you, as the PG hackers community, would be against a similar proposal for any reason, and if so why.
I'm not particularly against it, though if it can be solved with the
existing 'PROGRAM' capability then it may not make sense to complicate
the COPY code further.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2014-09-23 07:19:26 | superuser() shortcuts |
Previous Message | Heikki Linnakangas | 2014-09-23 06:53:26 | Re: Extending COPY TO |