From: | Roman Neuhauser <neuhauser(at)chello(dot)cz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: int4 -> unix timestamp -> sql timestamp; abstime? |
Date: | 2005-01-12 00:28:58 |
Message-ID: | 20050112002858.GE4463@isis.wad.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
# tgl(at)sss(dot)pgh(dot)pa(dot)us / 2005-01-11 18:35:18 -0500:
> Roman Neuhauser <neuhauser(at)chello(dot)cz> writes:
> > what is the opposite of cast(extract('epoch' from now()) as int)?
> > The only thing I found that works is
> > cast(cast(... as abstime) as timestamp)
> > and the documentation says abstime shouldn't be used, and may
> > disappear. What should I use instead?
>
> The recommended locution is
>
> SELECT TIMESTAMP WITH TIME ZONE 'epoch' + <x> * INTERVAL '1 second';
Have I missed this in the manual?
> Of course you can wrap this up in a function if you prefer (not sure why
> we haven't done so already).
I most surely will, and I'm glad to hear this will be included in 8.1.
Thanks for the replies!
--
FreeBSD 4.10-STABLE
1:25AM up 17:04, 9 users, load averages: 0.11, 0.06, 0.01
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-01-12 00:31:19 | Re: int4 -> unix timestamp -> sql timestamp; abstime? |
Previous Message | Michael Glaesemann | 2005-01-12 00:12:12 | Re: int4 -> unix timestamp -> sql timestamp; abstime? |