| From: | gkhan <drjohnpayne(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: to_timestamp alternatives |
| Date: | 2015-12-31 23:05:34 |
| Message-ID: | 1451603134115-5879753.post@n5.nabble.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Follow-up:
My initial question was about oddly-formatted date/times. The suggested
solution of casting directly to timestamp with ::timestamp is not as
flexible as the to_timestamp function that I was trying to avoid. For
example, this fails because of the day-before-month format:
SELECT ('18.09.2015 18:01:40')::timestamp
--ERROR: date/time field value out of range
whereas this works, but results in a timestamp *with* time zone that makes
assumptions about daylight savings times:
SELECT to_timestamp('18.09.2015 18:01:40','DD.MM.YYYY HH24:MI:SS')
I ended up with this simple solution, which does what I wanted to and avoids
time zones:
SELECT (to_date('18.09.2015','DD.MM.YYYY') ||' '||'18:01:40')::timestamp
Adrian: thanks for your observation about wildlife-human interactions --
that is a useful reminder since I'll be looking at traffic patterns.
--
View this message in context: http://postgresql.nabble.com/to-timestamp-alternatives-tp5879723p5879753.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-12-31 23:46:55 | Re: to_timestamp alternatives |
| Previous Message | Adrian Klaver | 2015-12-31 22:34:58 | Re: to_timestamp alternatives |