From: | Rodger Donaldson <rodgerd(at)diaspora(dot)gen(dot)nz> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | to_date has beaten me... |
Date: | 2003-02-06 04:02:48 |
Message-ID: | 20030206040247.GA8032@diaspora.gen.nz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Postgresql 7.2.3
insert
into log_entries
values (to_date('06/Feb/2003:11:29:11 +13', 'DD/Mon/YYYY:HH24:MI:SS'),0,302,
[... various other data elided ...]);
Always inserts the correct date, but sets the time to midnight.
Thinking this might be solved by shuffling with the source data, I've
tried such combinations as:
to_date('06/Feb/2003:11:29:11', 'DD/Mon/YYYY:HH24:MI:SS')
to_date('06/Feb/2003:11:29:11 +13', 'DD/Mon/YYYY:HH:MI:SS')
to_date('06/02/2003:11:29:11', 'DD/MM/YYYY:HH24:MI:SS')
...and so forth, but despite the column in question being a timestamp
with timszone, everything except the date gets truncated.
--
Rodger Donaldson rodgerd(at)diaspora(dot)gen(dot)nz
"My ATEX terminal isn't working"
"Is there power to the keyboard?"
"No, and it has smoke and flames coming out of it"
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-06 04:22:57 | Re: to_date has beaten me... |
Previous Message | codeWarrior | 2003-02-05 23:38:52 | Re: automatic time/user stamp - rule or trigger? |