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: Plan for CSV handling of quotes, NULL |
Date: | 2004-04-15 14:17:27 |
Message-ID: | 200404151417.i3FEHRY16358@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Andrew Dunstan wrote:
> Bruce Momjian said:
> > Andrew Dunstan wrote:
> >>
> >> copy mytable to 'mydata.csv' csv force zipcode;
> >>
> >> seems OK to me. I'm all in favor of low-tecH solutions where
> >> appropriate. ;-)
> >
> > Could we have FORCE just force quotes on all values, rather than
> > allowing a list of columns to be specified? Seems if you have a
> > strange zipcode field, it would be easier to just do them all.
> >
>
> Then dates and numbers would be wrong. No all or nothing switch will work.
OK, I will start coding. So FORCE col1, col2 will force quotes on those
two columns, right?
--
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-15 14:17:36 | Re: Plan for CSV handling of quotes, NULL |
Previous Message | Andrew Dunstan | 2004-04-15 09:32:52 | Re: Plan for CSV handling of quotes, NULL |