From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simone Tellini <tellini(at)areabusiness(dot)it>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: restore whoes |
Date: | 2002-02-11 06:02:29 |
Message-ID: | 200202110602.g1B62Tj07757@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-02-11 06:20:30 | Re: restore whoes |
Previous Message | Tom Lane | 2002-02-11 05:31:14 | Re: restore whoes |