From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Problem with COPY and DateStyle |
Date: | 2004-04-15 04:54:34 |
Message-ID: | 200404150454.i3F4sYP19285@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Never mind. I found out that pg_dump already does a SET datestyle =
'ISO' before dumping, so all the dates are in ISO format.
I just need to mention that COPY honors Datesyle.
---------------------------------------------------------------------------
pgman wrote:
> I just found out that datestyle affects the output of COPY, and hence
> pg_dump:
>
> test=> create table test(x date);
> CREATE
> test=> insert into test values ('2001-07-31');
> INSERT 17239 1
> test=> set datestyle to 'postgres, dmy';
> SET
> test=> copy test to '/tmp/x';
> COPY
> test=> \!cat /tmp/x
> 31-07-2001
> test=> set datestyle to 'postgres, mdy';
> SET
> test=> copy test to '/tmp/x';
> COPY
> test=> \!cat /tmp/x
> 07-31-2001
>
> Should we set the datestyle at the top of pg_dump files like we do with
> encoding and other settings? Seems we should.
>
> --
> 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
--
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 | Tom Lane | 2004-04-15 05:28:58 | Re: Problem with COPY and DateStyle |
Previous Message | Bruce Momjian | 2004-04-15 04:43:08 | Problem with COPY and DateStyle |