From: | Matthias Apitz <guru(at)unixarea(dot)de> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | Postgres general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Two small questions re/ COPY CSV data into table |
Date: | 2019-06-04 17:20:54 |
Message-ID: | 20190604172054.GA4376@sh4-5.1blu.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
El día Tuesday, June 04, 2019 a las 05:56:49PM +0100, Andrew Gierth escribió:
> Matthias> The new DELIMITER for PG is then vtab and the | is just a char in the
> Matthias> data (in the example above a pipe of two UNIX cmd).
>
> Yes, but why?
>
> If you use COPY ... WITH DELIMITER '|' (i.e. text mode, not CSV mode)
> then the \| is accepted as being a literal | and the unescaped | is
> treated as a delimiter. What is the point of the substitutions?
In the original data record in Sybase there is a column containing, i.e.
some UNIX print command to be read and executed by the application:
cmd | lpr ...
it is exported into the file as
cmd \| lpr ...
because the export delimiter is set to '|';
the COPY in text mode was complaining because it interpreted the |
of the sequence \| as an delimiter and the number of columns did not
matched.
I will provide tomorrow the exact input line, the exact COPY command and
the error.
matthias
--
Matthias Apitz, ✉ guru(at)unixarea(dot)de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2019-06-04 17:51:26 | Re: Two small questions re/ COPY CSV data into table |
Previous Message | paul.malm | 2019-06-04 17:18:45 | Re: psql \copy |