| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: multiline CSV fields |
| Date: | 2004-11-29 13:34:27 |
| Message-ID: | 200411291334.iATDYR603642@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan wrote:
> >OK, then should we disallow dumping out data in CVS format that we can't
> >load? Seems like the least we should do for 8.0.
> >
> >
> >
>
> As Tom rightly points out, having data make the round trip was not the
> goal of the exercise. Excel, for example, has no trouble reading such
> data (or at least my installation of it).
>
> Personally I consider CSVs with line end chars embedded in fields to be
> broken anyway, but this was something that was specifically mentioned
> when we were discussing requirements, which is why I coded for it.
OK, I am pretty uncomforable with this but you know this usage better
than I do. Should we issue a warning message stating it will not be
able to be reloaded?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-11-29 13:41:26 | Re: multiline CSV fields |
| Previous Message | Andrew Dunstan | 2004-11-29 13:27:48 | Re: multiline CSV fields |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-11-29 13:41:26 | Re: multiline CSV fields |
| Previous Message | Andrew Dunstan | 2004-11-29 13:27:48 | Re: multiline CSV fields |