Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > I think we should throw a very specific error from COPY when it sees \r
> > ending a line. Comments?
>
> Certainly *not*, as that is a valid data pattern. At present.
> See my proposal on pghackers for fixing this properly.
I was thinking of throwing a specific error when copy fails _and_ when
the line ends with a \r, rather than a generic COPY failure message ---
not sure how to do that, though.
I don't think I like the carriage-return -> \r solution anymore because
that would require people creating COPY files by hand, which I am sure
many do, to also escape carriage returns, which seems too MS-ish for me.
We would be hoisting stupid operating system principles on COPY file
creators.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
