From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Updated COPY CSV patch |
Date: | 2004-04-13 17:26:47 |
Message-ID: | 200404131726.i3DHQlj19502@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Andrew Dunstan wrote:
> >
> > I have two open issues. First, CSV should support WITH OIDS, no?
> >
>
> Why on earth would you want to? OIDs only have emaning to postgresql.
> Dumping to/from CSVs should not be seen as an alternative to Postgresql's
> normal text or binary file formats. Rather, it is a way of exchanging
> data with other programs that can't conveniently read or write those
> formats, but can read/write CSVs. I expect the data to be making a one
> way trip. OIDs make no sense to those other programs.
>
>
> For all those reasons I disallowed use of WITH OIDS for CSV mode.
>
> If you think that we should have it, it will be simple enough to do. It
> just strikes me as a very odd thing to do.
While doing OIDs seems atypical, it seems like a reasonable thing that
CSV should be able to do. Basically, I see no reason to disable it.
--
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 | Andrew Dunstan | 2004-04-13 17:31:13 | Re: Updated COPY CSV patch |
Previous Message | Andrew Dunstan | 2004-04-13 16:27:54 | Re: Updated COPY CSV patch |