From: Bruno Wolff III <bruno@wolff.to>
To: Joel Fradkin <jfradkin@wazagua.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: diference in dates in minutes
Date: Sat, 26 Feb 2005 15:16:10 -0600
Message-ID: <20050226211610.GA4472@wolff.to> (raw)
In-Reply-To: <000401c51c3f$b82188d0$797ba8c0@jfradkin>
References: <20050226180108.GB26473@wolff.to>
<000401c51c3f$b82188d0$797ba8c0@jfradkin>
On Sat, Feb 26, 2005 at 15:14:02 -0500,
Joel Fradkin <jfradkin@wazagua.com> wrote:
> You probably want to convert the dates to timestamps, subtract them to
> get an interval, extract the epoch to get timme in seconds and then divide
> by 60 to get time in minutes.
>
> The converting date to timestamp part isn't trivial. You need to decide
> on what you mean when you do this. If you really have timestamps in the
> first place, then you can skip the covernsion step.
>
> They are dates and I did find I could do date - date to give me an interval
> date_part('epoch',date-date) returns in secs so /60
date - date won't give you an interval, it will give you an integer of some
sort.
> This appeared to work ok without converting to time stamps, but maybe I am
> missing it if it is not correct as the example I looked at was a large
> difference. The app is analyzing Tlogs and the difference should never be
> too large, so I will further analyze it with real data.
> As always I appreciate the help.
> My real question is this an interval then and will it be depreciated soon?
The Interval type won't be depreciated. Using to_char to convert intervals
to strings is being depreciated. This won;t cause a problem for extract
or similar functions.
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: bruno@wolff.to, jfradkin@wazagua.com
Subject: Re: diference in dates in minutes
In-Reply-To: <20050226211610.GA4472@wolff.to>
* 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