Problem with COPY and DateStyle
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@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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-2001Should 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@candle.pha.pa.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@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Import Notes
Reply to msg id not found: | Resolved by subject fallback