pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Glaesemann <grzm@seespotcode.net>
To: Louis-David Mitterrand <vindex+lists-pgsql-sql@apartia.org>
Cc: pgsql-sql@postgresql.org
Subject: Re: EPOCH TIMESTAMP Conversion Problem
Date: Tue, 1 Jan 2008 14:32:25 -0500
Message-ID: <B0EE8783-066E-4A79-9E86-C3AD6411E45B@seespotcode.net> (raw)
In-Reply-To: <20080101142837.GA24772@apartia.fr>
References: <7e7750290711070237x7da14616i383ace7f513f0882@mail.gmail.com>
	<16805.1194449708@sss.pgh.pa.us>
	<20080101142837.GA24772@apartia.fr>


On Jan 1, 2008, at 9:28 , Louis-David Mitterrand wrote:

> On Wed, Nov 07, 2007 at 10:35:08AM -0500, Tom Lane wrote:
>> "Amitanand Chikorde" <amit99rs@gmail.com> writes:
>>> I want to convert MAX(mydate) from myTable to Epoch.
>>
>> Do you mean
>> 	SELECT EXTRACT(EPOCH FROM MAX(mydate)) FROM myTable
>
> Is using casts for the same purpose deprecated?
>
> 	SELECT current_date::timestamp::abstime::int4;

EXTRACT is SQL-standard syntax which appeals to some people. The ::  
casting syntax is a Postgres extension. And from the docs:

http://www.postgresql.org/docs/8.2/static/datatype-datetime.html

>  The types abstime  and reltime are lower precision types which are  
> used internally. You are discouraged from using these types in new  
> applications and are encouraged to move any old ones over when  
> appropriate. Any or all of these internal types might disappear in  
> a future release.


Michael Glaesemann
grzm seespotcode net





view thread (5+ messages)

Message-ID: <B0EE8783-066E-4A79-9E86-C3AD6411E45B@seespotcode.net>
Permalink:  ../B0EE8783-066E-4A79-9E86-C3AD6411E45B@seespotcode.net/
Also on:    postgresql.org/message-id/B0EE8783-066E-4A79-9E86-C3AD6411E45B@seespotcode.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: grzm@seespotcode.net, vindex+lists-pgsql-sql@apartia.org
  Subject: Re: EPOCH TIMESTAMP Conversion Problem
  In-Reply-To: <B0EE8783-066E-4A79-9E86-C3AD6411E45B@seespotcode.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox