From: | Jasen Betts <jasen(at)xnet(dot)co(dot)nz> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to typecast an integer into a timestamp? |
Date: | 2012-02-25 09:47:21 |
Message-ID: | jiaan9$r81$1@reversiblemaps.ath.cx |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2012-01-27, bboett(at)free(dot)fr <bboett(at)free(dot)fr> wrote:
> Hello!
>
> again quite a stupid problem i regularly run into....
> and that i still haven't solved yet...
>
> again i used a type timestamp to keep a track of modification time,
> and again it gets stupid and confusing.....
oops! (when recording events timestamp with timezone is usually best)
> first of all the errors are labeled as timestamp without timezone, i
> only specified timestamp....
it's the same thing since 8.1
> the data was created as a timestamp with php-mktime, but when
> sending to the database postgres complains that its an int, and when i
> try to typecast it, (with the ::timestamp appendix to the value), that
> its not possible to convert an int to a timestamp (without timezone)
> .....
> so as usual i would discard the timezone datatype and alter the
> table to use integer instead, but this time i am wondering, since this
> datatype is present, there's surely a way to use it properly? but how?
just use a string in this format "YYYY-MM-DD HH:MM:SS.sssssss +NN:NN"
--
⚂⚃ 100% natural
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2012-02-25 10:02:27 | Re: Stability in Windows? |
Previous Message | Jasen Betts | 2012-02-25 09:07:55 | Re: Behavior of subselects in target lists and order by |